summaryrefslogtreecommitdiffstats
path: root/drivers/i2c/busses/Makefile
diff options
context:
space:
mode:
authorWolfram Sang <wsa@the-dreams.de>2014-06-01 22:35:25 +0200
committerWolfram Sang <wsa@the-dreams.de>2014-06-02 19:18:37 +0200
commit7da62cb1853025a579a8942fc4d7c9dee6afb73e (patch)
treee3b3a048bd850364289f7fbc424188a94de9815b /drivers/i2c/busses/Makefile
parent9b2a6da33ccb1bc0d68f4319cef7c7299727ac4d (diff)
downloadlinux-7da62cb1853025a579a8942fc4d7c9dee6afb73e.tar.bz2
i2c: nuc900: remove driver
Arnd said in another patch: "As far as I can tell, this driver must have produced this error for as long as it has been merged into the mainline kernel, but it was never part of the normal build tests: drivers/i2c/busses/i2c-nuc900.c: In function 'nuc900_i2c_probe': drivers/i2c/busses/i2c-nuc900.c:601:17: error: request for member 'apbfreq' in something not a structure or union ret = (i2c->clk.apbfreq)/(pdata->bus_freq * 5) - 1; ^ This is an attempt to get the driver to build and possibly work correctly, although I do wonder whether we should just remove it, as it has clearly never worked." I agree with removing it since nobody showed interest in Arnd's fixup patch. Reported-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Wolfram Sang <wsa@the-dreams.de> Cc: Wan ZongShun <mcuos.com@gmail.org> Acked-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'drivers/i2c/busses/Makefile')
-rw-r--r--drivers/i2c/busses/Makefile1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/i2c/busses/Makefile b/drivers/i2c/busses/Makefile
index 18d18ff9db93..413d062a08f8 100644
--- a/drivers/i2c/busses/Makefile
+++ b/drivers/i2c/busses/Makefile
@@ -55,7 +55,6 @@ obj-$(CONFIG_I2C_MPC) += i2c-mpc.o
obj-$(CONFIG_I2C_MV64XXX) += i2c-mv64xxx.o
obj-$(CONFIG_I2C_MXS) += i2c-mxs.o
obj-$(CONFIG_I2C_NOMADIK) += i2c-nomadik.o
-obj-$(CONFIG_I2C_NUC900) += i2c-nuc900.o
obj-$(CONFIG_I2C_OCORES) += i2c-ocores.o
obj-$(CONFIG_I2C_OMAP) += i2c-omap.o
obj-$(CONFIG_I2C_PASEMI) += i2c-pasemi.o