lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 16 Jan 2017 12:23:44 -0800
From:   John Stultz <>
To:     Felipe Balbi <>
Cc:     lkml <>, Wei Xu <>,
        Guodong Xu <>,
        Amit Pundir <>,
        Rob Herring <>,
        John Youn <>,
        Douglas Anderson <>,
        Chen Yu <>,
        Vardan Mikayelyan <>,
        Kishon Vijay Abraham I <>,
        Greg Kroah-Hartman <>,
        Linux USB List <>
Subject: Re: [RFC][PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board

On Mon, Jan 16, 2017 at 2:29 AM, Felipe Balbi
<> wrote:
> Hi,
> John Stultz <> 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?


Powered by blists - more mailing lists