Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2018-03-24 Thread Wolfram Sang
On Fri, Mar 23, 2018 at 03:39:47AM +, Chris Packham wrote: > On 07/12/17 23:42, Wolfram Sang wrote: > > On Sun, Oct 29, 2017 at 06:29:18PM +0100, Wolfram Sang wrote: > >> On Wed, Jul 05, 2017 at 10:13:54PM +1200, Chris Packham wrote: > >>> This series addresses some of the points identified by

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2018-03-24 Thread Wolfram Sang
On Fri, Mar 23, 2018 at 03:39:47AM +, Chris Packham wrote: > On 07/12/17 23:42, Wolfram Sang wrote: > > On Sun, Oct 29, 2017 at 06:29:18PM +0100, Wolfram Sang wrote: > >> On Wed, Jul 05, 2017 at 10:13:54PM +1200, Chris Packham wrote: > >>> This series addresses some of the points identified by

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2018-03-23 Thread Wolfram Sang
On Fri, Mar 23, 2018 at 03:39:47AM +, Chris Packham wrote: > On 07/12/17 23:42, Wolfram Sang wrote: > > On Sun, Oct 29, 2017 at 06:29:18PM +0100, Wolfram Sang wrote: > >> On Wed, Jul 05, 2017 at 10:13:54PM +1200, Chris Packham wrote: > >>> This series addresses some of the points identified by

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2018-03-23 Thread Wolfram Sang
On Fri, Mar 23, 2018 at 03:39:47AM +, Chris Packham wrote: > On 07/12/17 23:42, Wolfram Sang wrote: > > On Sun, Oct 29, 2017 at 06:29:18PM +0100, Wolfram Sang wrote: > >> On Wed, Jul 05, 2017 at 10:13:54PM +1200, Chris Packham wrote: > >>> This series addresses some of the points identified by

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2018-03-22 Thread Chris Packham
On 07/12/17 23:42, Wolfram Sang wrote: > On Sun, Oct 29, 2017 at 06:29:18PM +0100, Wolfram Sang wrote: >> On Wed, Jul 05, 2017 at 10:13:54PM +1200, Chris Packham wrote: >>> This series addresses some of the points identified by Andy. The series is >>> based on top of i2c/for-next. 2 of the patches

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2018-03-22 Thread Chris Packham
On 07/12/17 23:42, Wolfram Sang wrote: > On Sun, Oct 29, 2017 at 06:29:18PM +0100, Wolfram Sang wrote: >> On Wed, Jul 05, 2017 at 10:13:54PM +1200, Chris Packham wrote: >>> This series addresses some of the points identified by Andy. The series is >>> based on top of i2c/for-next. 2 of the patches

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2017-12-07 Thread Wolfram Sang
On Sun, Oct 29, 2017 at 06:29:18PM +0100, Wolfram Sang wrote: > On Wed, Jul 05, 2017 at 10:13:54PM +1200, Chris Packham wrote: > > This series addresses some of the points identified by Andy. The series is > > based on top of i2c/for-next. 2 of the patches from v1 have already been > > applied so

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2017-12-07 Thread Wolfram Sang
On Sun, Oct 29, 2017 at 06:29:18PM +0100, Wolfram Sang wrote: > On Wed, Jul 05, 2017 at 10:13:54PM +1200, Chris Packham wrote: > > This series addresses some of the points identified by Andy. The series is > > based on top of i2c/for-next. 2 of the patches from v1 have already been > > applied so

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2017-10-29 Thread Wolfram Sang
On Wed, Jul 05, 2017 at 10:13:54PM +1200, Chris Packham wrote: > This series addresses some of the points identified by Andy. The series is > based on top of i2c/for-next. 2 of the patches from v1 have already been > applied so I've dropped them from this version. > > I have compile tested patch

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2017-10-29 Thread Wolfram Sang
On Wed, Jul 05, 2017 at 10:13:54PM +1200, Chris Packham wrote: > This series addresses some of the points identified by Andy. The series is > based on top of i2c/for-next. 2 of the patches from v1 have already been > applied so I've dropped them from this version. > > I have compile tested patch

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2017-07-05 Thread Chris Packham
On 05/07/17 23:49, Andy Shevchenko wrote: > On Wed, Jul 5, 2017 at 1:13 PM, Chris Packham > wrote: >> This series addresses some of the points identified by Andy. The series is >> based on top of i2c/for-next. 2 of the patches from v1 have already been >>

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2017-07-05 Thread Chris Packham
On 05/07/17 23:49, Andy Shevchenko wrote: > On Wed, Jul 5, 2017 at 1:13 PM, Chris Packham > wrote: >> This series addresses some of the points identified by Andy. The series is >> based on top of i2c/for-next. 2 of the patches from v1 have already been >> applied so I've dropped them from this

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2017-07-05 Thread Andy Shevchenko
On Wed, Jul 5, 2017 at 1:13 PM, Chris Packham wrote: > This series addresses some of the points identified by Andy. The series is > based on top of i2c/for-next. 2 of the patches from v1 have already been > applied so I've dropped them from this version. > > I

Re: [PATCH v2 0/4] i2c: pca-platform: additional improvements

2017-07-05 Thread Andy Shevchenko
On Wed, Jul 5, 2017 at 1:13 PM, Chris Packham wrote: > This series addresses some of the points identified by Andy. The series is > based on top of i2c/for-next. 2 of the patches from v1 have already been > applied so I've dropped them from this version. > > I have compile tested patch 1/1 but I

[PATCH v2 0/4] i2c: pca-platform: additional improvements

2017-07-05 Thread Chris Packham
This series addresses some of the points identified by Andy. The series is based on top of i2c/for-next. 2 of the patches from v1 have already been applied so I've dropped them from this version. I have compile tested patch 1/1 but I don't have access to sh hardware to actually test the changes

[PATCH v2 0/4] i2c: pca-platform: additional improvements

2017-07-05 Thread Chris Packham
This series addresses some of the points identified by Andy. The series is based on top of i2c/for-next. 2 of the patches from v1 have already been applied so I've dropped them from this version. I have compile tested patch 1/1 but I don't have access to sh hardware to actually test the changes