linux-kernel - Re: [GIT PULL] arm64: dts: samsung: Second pull for v5.17

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: <CAOesGMgF3S5_XsWjEqq=-zfYXwOWFpFNA6afL81wceRUA_0FeQ@mail.gmail.com>
Date:   Wed, 19 Jan 2022 08:53:05 -0800
From:   Olof Johansson <olof@...om.net>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Sam Protsenko <semen.protsenko@...aro.org>,
        arm-soc <arm@...nel.org>, SoC Team <soc@...nel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        "moderated list:ARM/SAMSUNG EXYNOS ARM ARCHITECTURES" 
        <linux-samsung-soc@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Krzysztof Kozlowski <krzk@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
Subject: Re: [GIT PULL] arm64: dts: samsung: Second pull for v5.17

On Wed, Jan 19, 2022 at 8:07 AM Arnd Bergmann <arnd@...db.de> wrote:
>
> On Wed, Jan 19, 2022 at 4:11 PM Sam Protsenko
> <semen.protsenko@...aro.org> wrote:
> > On Mon, 27 Dec 2021 at 13:30, Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com> wrote:
> >
> > Hi Olof, Arnd,
> >
> > Just want to check if it's possible for those patches to be applied in
> > v5.17? Sorry for the noise, but that's important to me.
>
> I can see that Olof merged merged this into the "arm/late" branch in
> the soc tree,
> so I assume he still plans to send it in the next few days.

Yep, will be sent up today most likely.

> With the timing over Christmas, I sent out the large bulk of the
> contents (anything
> I merged before Dec 23) last year, and Linus already merged it, the rest ended
> up in the "late" branch.
>
> As usual, there is no guarantee that late changes make it in, but I have seen
> no indication of any problems so far.

Correct. Been sitting on it for a while in case there were fixes
coming in for the first pieces that got merged, but in traditional
fashion I'm guessing those will start to show up a few days after the
late branch gets merged. :)


-Olof