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


Groups > linux.kernel > #1559622 > unrolled thread

Re: [RFC][PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board

Started byFelipe Balbi <felipe.balbi@linux.intel.com>
First post2017-01-16 11:40 +0100
Last post2017-01-16 21:30 +0100
Articles 2 — 2 participants

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: [RFC][PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board Felipe Balbi <felipe.balbi@linux.intel.com> - 2017-01-16 11:40 +0100
    Re: [RFC][PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board John Stultz <john.stultz@linaro.org> - 2017-01-16 21:30 +0100

#1559622 — Re: [RFC][PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board

FromFelipe Balbi <felipe.balbi@linux.intel.com>
Date2017-01-16 11:40 +0100
SubjectRe: [RFC][PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board
Message-ID<t0cRJ-7Aa-33@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hi,

John Stultz <john.stultz@linaro.org> writes:
> I just wanted to re-send my current queue of patches for dwc2
> controller on the HiKey board, as my last patchset ended up
> colliding with a number of changes that landed in the 4.10-rc
> merge window. 
>
> I've fixed things up and validated these against HiKey. I also
> made a small change to one of the patches as suggested by Vardan.
>
> This does exclude my patchset[1] to add extcon support to dwc2,
> which John Youn suspects a pending rework of the dwc2 fifo init
> logic might make unnecssary (however, no such changes appeared
> to have landed in 4.10-rc, so I'm still using that patchset in
> my testing).
>
> I'm also out for the holidays after today, and while I suspect
> others are likely going to be out as well, I figured I'd send
> these out for a chance at review, rather then sit on them for
> two weeks. I'll resend after the new year addressing any
> feedback I do get though.
>
> Feedback would be greatly appreciated!

John Y, any comments?

-- 
balbi

[toc] | [next] | [standalone]


#1560038

FromJohn Stultz <john.stultz@linaro.org>
Date2017-01-16 21:30 +0100
Message-ID<t0m4F-5H7-1@gated-at.bofh.it>
In reply to#1559622
On Mon, Jan 16, 2017 at 2:29 AM, Felipe Balbi
<felipe.balbi@linux.intel.com> wrote:
>
> Hi,
>
> John Stultz <john.stultz@linaro.org> writes:
>> I just wanted to re-send my current queue of patches for dwc2
>> controller on the HiKey board, as my last patchset ended up
>> colliding with a number of changes that landed in the 4.10-rc
>> merge window.
>>
>> I've fixed things up and validated these against HiKey. I also
>> made a small change to one of the patches as suggested by Vardan.
>>
>> This does exclude my patchset[1] to add extcon support to dwc2,
>> which John Youn suspects a pending rework of the dwc2 fifo init
>> logic might make unnecssary (however, no such changes appeared
>> to have landed in 4.10-rc, so I'm still using that patchset in
>> my testing).
>>
>> I'm also out for the holidays after today, and while I suspect
>> others are likely going to be out as well, I figured I'd send
>> these out for a chance at review, rather then sit on them for
>> two weeks. I'll resend after the new year addressing any
>> feedback I do get though.
>>
>> Feedback would be greatly appreciated!
>
> John Y, any comments?

So from this JohnY submitted one patch for 4.10-rc (which hasn't yet
landed) and suggested I re-spin the other 4 on top of his for-next
branch. However, that patchset you said doesn't apply to your tree.

Its not really clear who's tree I should be targeting here?

thanks
-john

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web