Re: [PATCH 0/2] i2c: move include files out of include/linux/i2c

2017-07-14 Thread Wolfram Sang
Hi peda, > I don't seem to have this series in my inbox and not in my i2c folder either? You have been CCed on the patches, but not on the cover-letter. Sorry about that. > patchwork and then I found it in the branch too, but in patchwork it has the > expected "i2c: mux: " prefix so I'm not sure

Re: [PATCH 0/2] i2c: move include files out of include/linux/i2c

2017-07-13 Thread Peter Rosin
On 2017-07-13 11:46, Wolfram Sang wrote: > Hi peda, > > On Sun, May 21, 2017 at 10:37:41PM +0200, Wolfram Sang wrote: >> It doesn't make sense to use include/linux/i2c for client drivers which may >> in >> fact rather be hwmon or input or whatever devices. As a result, I want to >> deprecate incl

Re: [PATCH 0/2] i2c: move include files out of include/linux/i2c

2017-07-13 Thread Wolfram Sang
Hi peda, On Sun, May 21, 2017 at 10:37:41PM +0200, Wolfram Sang wrote: > It doesn't make sense to use include/linux/i2c for client drivers which may in > fact rather be hwmon or input or whatever devices. As a result, I want to > deprecate include/linux/i2c for good. This series moves the include

[PATCH 0/2] i2c: move include files out of include/linux/i2c

2017-05-21 Thread Wolfram Sang
It doesn't make sense to use include/linux/i2c for client drivers which may in fact rather be hwmon or input or whatever devices. As a result, I want to deprecate include/linux/i2c for good. This series moves the include files to a better location, largely include/platform_data because that is what