From: Andreas Kemnade <andreas@kemnade.info>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: grygorii.strashko@ti.com, ssantosh@kernel.org,
khilman@kernel.org, brgl@bgdev.pl, linux-omap@vger.kernel.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: omap: use dynamic allocation of base
Date: Mon, 16 Jan 2023 18:08:13 +0100 [thread overview]
Message-ID: <20230116180813.08cb1fb0@aktux> (raw)
In-Reply-To: <CACRpkdauDEys-XyYvb=jt1U6FcKc-qiie-A3W0WQ08rnm42DwQ@mail.gmail.com>
Hi,
On Mon, 16 Jan 2023 15:24:42 +0100
Linus Walleij <linus.walleij@linaro.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
prev parent reply other threads:[~2023-01-16 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 20:59 [PATCH] gpio: omap: use dynamic allocation of base Andreas Kemnade
2023-01-16 8:38 ` Bartosz Golaszewski
2023-01-16 17:14 ` Tony Lindgren
2024-08-29 8:52 ` Richard Weinberger
2024-08-30 22:46 ` Linus Walleij
2024-08-31 7:32 ` Richard Weinberger
2023-01-16 14:24 ` Linus Walleij
2023-01-16 17:08 ` Andreas Kemnade [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230116180813.08cb1fb0@aktux \
--to=andreas@kemnade.info \
--cc=brgl@bgdev.pl \
--cc=grygorii.strashko@ti.com \
--cc=khilman@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ssantosh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox