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
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
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
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
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
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
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
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
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
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
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
>>
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
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
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
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
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
16 matches
Mail list logo