linux-kernel - Re: [PATCH] gpio: omap: use dynamic allocation of base

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]

Date:   Mon, 16 Jan 2023 18:08:13 +0100
From:   Andreas Kemnade <andreas@...nade.info>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     grygorii.strashko@...com, ssantosh@...nel.org, khilman@...nel.org,
        brgl@...ev.pl, linux-omap@...r.kernel.org,
        linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] gpio: omap: use dynamic allocation of base

Hi,

On Mon, 16 Jan 2023 15:24:42 +0100
Linus Walleij <linus.walleij@...aro.org> wrote:

> > maybe CC stable? not sure about good fixes tag.  
> 
> I wouldn't do that from the outset. If there are no problems
> for a few kernel releases we can think about doing that.

I have the impression that numbering somehow changed here.
In earlier kernel, omap_gpmc started at >400 and gpio-twl4030 also
(both base = -1 now), so no conflicts with the static allocation of
the soc-gpios.  I have not investigated/bisected yet. But perhaps
additionally, a patch ensuring that dynamic allocation starts at
a higher number to not interfer with static numbering with be interesting.

That could then be more easily backportable.

Regards,
Andreas