[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VdmN2wqwwnea0gtTQJ+Y5twQaJp6iEL2esEMCHDi8bvVg@mail.gmail.com>
Date: Fri, 7 Feb 2025 14:20:16 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Ulf Hansson <ulf.hansson@...aro.org>
Cc: Bartosz Golaszewski <brgl@...ev.pl>, David Lechner <dlechner@...libre.com>,
Linus Walleij <linus.walleij@...aro.org>, Andy Shevchenko <andy@...nel.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>, Lars-Peter Clausen <lars@...afoo.de>,
Michael Hennerich <Michael.Hennerich@...log.com>, Jonathan Cameron <jic23@...nel.org>,
Peter Rosin <peda@...ntia.se>, Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Vinod Koul <vkoul@...nel.org>, Kishon Vijay Abraham I <kishon@...nel.org>, Nuno Sá <nuno.sa@...log.com>,
Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>,
Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
linux-mmc@...r.kernel.org, netdev@...r.kernel.org,
linux-phy@...ts.infradead.org, linux-sound@...r.kernel.org
Subject: Re: [PATCH v2 00/13] gpiolib: add gpiod_multi_set_value_cansleep
On Fri, Feb 7, 2025 at 11:48 AM Ulf Hansson <ulf.hansson@...aro.org> wrote:
> On Fri, 7 Feb 2025 at 08:49, Bartosz Golaszewski <brgl@...ev.pl> wrote:
> > On Thu, Feb 6, 2025 at 11:48 PM David Lechner <dlechner@...libre.com> wrote:
...
> > > Maintainers, if you prefer to have this go through the gpio tree, please
> > > give your Acked-by:, otherwise I will resend what is left after the next
> > > kernel release.
> > I can provide an immutable branch for the entire series for everyone
> > to pull or I can apply patch one, provide an immutable branch and
> > every subsystem can take their respective patches. What do you prefer?
>
> The changes look small and trivial to me. I wouldn't mind if you take
> them all (at least for mmc). An immutable branch would be good, if it
> turns out that we need to pull them.
+1 here, the potential user for immutable branch/tag is IIO.
The rest looks trivial and unlikely to have conflicts.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists