lists.openwall.net   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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <79fed88c-7dae-4131-a005-b8374b5fe660@www.fastmail.com>
Date:   Thu, 22 Sep 2022 23:22:07 +0200
From:   "Arnd Bergmann" <arnd@...db.de>
To:     "Florian Fainelli" <f.fainelli@...il.com>,
        "Linus Torvalds" <torvalds@...ux-foundation.org>
Cc:     soc@...nel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] ARM: SoC fixes for 6.0-rc6

On Thu, Sep 22, 2022, at 8:17 PM, Florian Fainelli wrote:
> On 9/22/22 11:13, Linus Torvalds wrote:
>> I could pull your Broadcom fixes directly on top if you/Arnd would
>> prefer that as a solution?
>
> Thanks for the offer, no real urgency on my side, if there is a -rc7, 
> maybe Arnd can submit a follow up for ARM SoC fixes, as there is a good 
> chance we will accumulate more of those between -rc6 and then. If not, 
> and Arnd is fine with it, yes please pull mine directly, thanks!

Yes, that was my plan already, sorry for not making that clearer already:

I still have a couple of fixes pull requests in a backlog, including
yours. Since the fixes branch was already large and the rest has
not been in my tree yet, I decided to send whatever I had already,
but planned to pick the rest up tomorrow morning to send early next
week after I get a successful test result from the build bots.

      Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ