linux-kernel - Re: [GIT PULL] pin control fixes for the v5.17 series

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: <CACRpkdY-8D8ZYy9VichQmJHTJCSskFs=e0qpbYssf7tED_9dLw@mail.gmail.com>
Date:   Mon, 28 Feb 2022 23:49:56 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Hans Verkuil <hverkuil@...all.nl>,
        Guenter Roeck <linux@...ck-us.net>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>
Subject: Re: [GIT PULL] pin control fixes for the v5.17 series

On Mon, Feb 28, 2022 at 8:15 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:

> Well, part of me being confused is that I've literally seen you reply
> with 'patch applied' to the fixes.. Ie:
>
>     https://lore.kernel.org/lkml/CACRpkdZ1nFAmzRvsvKvZ08fsP_MgsnsiNpD7LdRRXUDWtO_w=Q@mail.gmail.com/
>
> but then I didn't get the result.
>
> Afaik, that patch is only relevant if you applied the previous fix
> ("pinctrl-sunxi: use the right offset" or something like that).

Yes this is the issue, reading that patch series does not really make it
clear that it should be applied, also it gets into next through something that
is not my tree so I get a bit confused and feel a bit out of control here.

Anyways I will apply that patch:

> I get the feeling that you didn't realize that this was a 5.17 issue,
> and have maybe applied them to the wrong branch, and they are pending
> for the next merge window.

Indeed.

The Fixes tag on the latter patch refers to another commit
entirely so it was applied on its own merits, for next.

I'll take these two:

pinctrl-sunxi: sunxi_pinctrl_gpio_direction_in/output: use correct offset
pinctrl: sunxi: Use unique lockdep classes for IRQs

and put them into fixes, that should nail it.

Yours,
Linus Walleij