On Mon, Jul 10, 2017 at 10:07 AM, Lee Jones wrote:
> On Mon, 10 Jul 2017, Javier Martinez Canillas wrote:
>
>> Hello Lee,
>>
>> On Thu, Jun 15, 2017 at 8:49 PM, Javier Martinez Canillas
>> wrote:
>> >
>> > This series add OF device ID tables to mfd I2C
On Mon, Jul 10, 2017 at 10:07 AM, Lee Jones wrote:
> On Mon, 10 Jul 2017, Javier Martinez Canillas wrote:
>
>> Hello Lee,
>>
>> On Thu, Jun 15, 2017 at 8:49 PM, Javier Martinez Canillas
>> wrote:
>> >
>> > This series add OF device ID tables to mfd I2C drivers whose devices are
>> > either used
On Mon, 10 Jul 2017, Javier Martinez Canillas wrote:
> Hello Lee,
>
> On Thu, Jun 15, 2017 at 8:49 PM, Javier Martinez Canillas
> wrote:
> >
> > This series add OF device ID tables to mfd I2C drivers whose devices are
> > either used in Device Tree source files or are
On Mon, 10 Jul 2017, Javier Martinez Canillas wrote:
> Hello Lee,
>
> On Thu, Jun 15, 2017 at 8:49 PM, Javier Martinez Canillas
> wrote:
> >
> > This series add OF device ID tables to mfd I2C drivers whose devices are
> > either used in Device Tree source files or are listed in binding docs as
Hello Lee,
On Thu, Jun 15, 2017 at 8:49 PM, Javier Martinez Canillas
wrote:
>
> This series add OF device ID tables to mfd I2C drivers whose devices are
> either used in Device Tree source files or are listed in binding docs as
> a compatible string.
>
> That's done because
Hello Lee,
On Thu, Jun 15, 2017 at 8:49 PM, Javier Martinez Canillas
wrote:
>
> This series add OF device ID tables to mfd I2C drivers whose devices are
> either used in Device Tree source files or are listed in binding docs as
> a compatible string.
>
> That's done because the plan is to change
Hello,
This series add OF device ID tables to mfd I2C drivers whose devices are
either used in Device Tree source files or are listed in binding docs as
a compatible string.
That's done because the plan is to change the I2C core to report proper OF
modaliases instead of always reporting a
Hello,
This series add OF device ID tables to mfd I2C drivers whose devices are
either used in Device Tree source files or are listed in binding docs as
a compatible string.
That's done because the plan is to change the I2C core to report proper OF
modaliases instead of always reporting a
Hello Lee,
On Fri, May 5, 2017 at 12:40 PM, Javier Martinez Canillas
wrote:
> Hello,
>
> On Thu, May 4, 2017 at 1:50 PM, Lee Jones wrote:
>> On Thu, 04 May 2017, Wolfram Sang wrote:
>>> thanks for the series.
>>>
>>> > Most patches can be applied
Hello Lee,
On Fri, May 5, 2017 at 12:40 PM, Javier Martinez Canillas
wrote:
> Hello,
>
> On Thu, May 4, 2017 at 1:50 PM, Lee Jones wrote:
>> On Thu, 04 May 2017, Wolfram Sang wrote:
>>> thanks for the series.
>>>
>>> > Most patches can be applied independently, with the exception of patches
>>>
Hello,
On Thu, May 4, 2017 at 1:50 PM, Lee Jones wrote:
> On Thu, 04 May 2017, Wolfram Sang wrote:
>> thanks for the series.
>>
>> > Most patches can be applied independently, with the exception of patches
>> > 2 to 4 that should be applied in the same tree to keep
Hello,
On Thu, May 4, 2017 at 1:50 PM, Lee Jones wrote:
> On Thu, 04 May 2017, Wolfram Sang wrote:
>> thanks for the series.
>>
>> > Most patches can be applied independently, with the exception of patches
>> > 2 to 4 that should be applied in the same tree to keep bisect-ability. I
>> > suggest
On Thu, 04 May 2017, Wolfram Sang wrote:
> thanks for the series.
>
> > Most patches can be applied independently, with the exception of patches
> > 2 to 4 that should be applied in the same tree to keep bisect-ability. I
> > suggest these to go through the MFD subsystem tree.
>
> From my POV,
On Thu, 04 May 2017, Wolfram Sang wrote:
> thanks for the series.
>
> > Most patches can be applied independently, with the exception of patches
> > 2 to 4 that should be applied in the same tree to keep bisect-ability. I
> > suggest these to go through the MFD subsystem tree.
>
> From my POV,
Javier,
thanks for the series.
> Most patches can be applied independently, with the exception of patches
> 2 to 4 that should be applied in the same tree to keep bisect-ability. I
> suggest these to go through the MFD subsystem tree.
From my POV, patches 2-5 should be applied to the same tree.
Javier,
thanks for the series.
> Most patches can be applied independently, with the exception of patches
> 2 to 4 that should be applied in the same tree to keep bisect-ability. I
> suggest these to go through the MFD subsystem tree.
From my POV, patches 2-5 should be applied to the same tree.
Hello,
This series add OF device ID tables to mfd I2C drivers whose devices are
either used in Device Tree source files or are listed in binding docs as
a compatible string.
That's done because the plan is to change the I2C core to report proper OF
modaliases instead of always reporting a
Hello,
This series add OF device ID tables to mfd I2C drivers whose devices are
either used in Device Tree source files or are listed in binding docs as
a compatible string.
That's done because the plan is to change the I2C core to report proper OF
modaliases instead of always reporting a
18 matches
Mail list logo