Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1461460 > unrolled thread

Re: [PATCH v5 0/5] da8xx USB PHY platform devices and clocks (was "da8xx UBS clocks")

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v5 0/5] da8xx USB PHY platform devices and clocks (was  "da8xx UBS clocks") Kevin Hilman <khilman@kernel.org> - 2016-08-12 23:30 +0200
    Re: [PATCH v5 0/5] da8xx USB PHY platform devices and clocks (was  "da8xx UBS clocks") Kishon Vijay Abraham I <kishon@ti.com> - 2016-08-17 11:40 +0200
      Re: [PATCH v5 0/5] da8xx USB PHY platform devices and clocks (was  "da8xx UBS clocks") Kevin Hilman <khilman@kernel.org> - 2016-08-19 18:50 +0200
        Re: [PATCH v5 0/5] da8xx USB PHY platform devices and clocks (was  "da8xx UBS clocks") David Lechner <david@lechnology.com> - 2016-08-19 19:00 +0200

#1461460 — Re: [PATCH v5 0/5] da8xx USB PHY platform devices and clocks (was "da8xx UBS clocks")

On Wed, May 25, 2016 at 6:18 AM, Sekhar Nori <nsekhar@ti.com> wrote:
> On Monday 23 May 2016 08:44 PM, David Lechner wrote:
>> On 05/09/2016 06:46 PM, David Lechner wrote:
>>> v5 changes: renamed "usbphy" to "usb_phy" or "usb-phy" as appropriate
>>>

[...]

>>
>> What should I be doing to keep this moving along?
>
> We need the related driver changes to be applied first. I could then use
> an immutable branch to push the platform changes against.
>
> I did take a look at the patches and they look good to me. Except the
> one comment from Sergei which I just now indicated that I agree with.

Just checking on the status of this.  I'm not seeing the driver
changes in mainline yet.

Any update?

Kevin

[toc] | [next] | [standalone]

#1464445

Hi Kevin,

On Saturday 13 August 2016 02:54 AM, Kevin Hilman wrote:
> On Wed, May 25, 2016 at 6:18 AM, Sekhar Nori <nsekhar@ti.com> wrote:
>> On Monday 23 May 2016 08:44 PM, David Lechner wrote:
>>> On 05/09/2016 06:46 PM, David Lechner wrote:
>>>> v5 changes: renamed "usbphy" to "usb_phy" or "usb-phy" as appropriate
>>>>
> 
> [...]
> 
>>>
>>> What should I be doing to keep this moving along?
>>
>> We need the related driver changes to be applied first. I could then use
>> an immutable branch to push the platform changes against.
>>
>> I did take a look at the patches and they look good to me. Except the
>> one comment from Sergei which I just now indicated that I agree with.
> 
> Just checking on the status of this.  I'm not seeing the driver
> changes in mainline yet.
> 
> Any update?

phy driver is already merged which actually introduced a compilation error. The
fix for it is currently queued in linux-phy -fixes and it should be merged in
this -rc cycle.
I think it would be better if David Lechner re-spins the series re-based on top
of latest mainline kernel and then merged by Bin/Alan.

Thanks
Kishon

[toc] | [prev] | [next] | [standalone]

#1466557

David,

On Wed, Aug 17, 2016 at 4:35 AM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>
> Hi Kevin,
>
> On Saturday 13 August 2016 02:54 AM, Kevin Hilman wrote:
> > On Wed, May 25, 2016 at 6:18 AM, Sekhar Nori <nsekhar@ti.com> wrote:
> >> On Monday 23 May 2016 08:44 PM, David Lechner wrote:
> >>> On 05/09/2016 06:46 PM, David Lechner wrote:
> >>>> v5 changes: renamed "usbphy" to "usb_phy" or "usb-phy" as appropriate
> >>>>
> >
> > [...]
> >
> >>>
> >>> What should I be doing to keep this moving along?
> >>
> >> We need the related driver changes to be applied first. I could then use
> >> an immutable branch to push the platform changes against.
> >>
> >> I did take a look at the patches and they look good to me. Except the
> >> one comment from Sergei which I just now indicated that I agree with.
> >
> > Just checking on the status of this.  I'm not seeing the driver
> > changes in mainline yet.
> >
> > Any update?
>
> phy driver is already merged which actually introduced a compilation error. The
> fix for it is currently queued in linux-phy -fixes and it should be merged in
> this -rc cycle.
> I think it would be better if David Lechner re-spins the series re-based on top
> of latest mainline kernel and then merged by Bin/Alan.

Does this work for you?

Kevin

[toc] | [prev] | [next] | [standalone]

#1466561

On 08/19/2016 11:40 AM, Kevin Hilman wrote:
> David,
>
> On Wed, Aug 17, 2016 at 4:35 AM, Kishon Vijay Abraham I <kishon@ti.com> wrote:
>>
>> Hi Kevin,
>>
>> On Saturday 13 August 2016 02:54 AM, Kevin Hilman wrote:
>>> On Wed, May 25, 2016 at 6:18 AM, Sekhar Nori <nsekhar@ti.com> wrote:
>>>> On Monday 23 May 2016 08:44 PM, David Lechner wrote:
>>>>> On 05/09/2016 06:46 PM, David Lechner wrote:
>>>>>> v5 changes: renamed "usbphy" to "usb_phy" or "usb-phy" as appropriate
>>>>>>
>>>
>>> [...]
>>>
>>>>>
>>>>> What should I be doing to keep this moving along?
>>>>
>>>> We need the related driver changes to be applied first. I could then use
>>>> an immutable branch to push the platform changes against.
>>>>
>>>> I did take a look at the patches and they look good to me. Except the
>>>> one comment from Sergei which I just now indicated that I agree with.
>>>
>>> Just checking on the status of this.  I'm not seeing the driver
>>> changes in mainline yet.
>>>
>>> Any update?
>>
>> phy driver is already merged which actually introduced a compilation error. The
>> fix for it is currently queued in linux-phy -fixes and it should be merged in
>> this -rc cycle.
>> I think it would be better if David Lechner re-spins the series re-based on top
>> of latest mainline kernel and then merged by Bin/Alan.
>
> Does this work for you?
>
> Kevin
>


Yes, I try to get this done in the next few days.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web