From: Philipp Zabel <p.zabel@pengutronix.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v6 0/8] reset: rework reset-gpios handling
Date: Thu, 13 Nov 2025 11:30:39 +0100 [thread overview]
Message-ID: <7aa5a0ce599f86cc29e5075aa4e35155dfcd013e.camel@pengutronix.de> (raw)
In-Reply-To: <CAMRc=Mfcir56ZizXgZZpt4nQY234PA9jx3CQ24YCVQJFBQ7msA@mail.gmail.com>
On Mo, 2025-11-10 at 17:57 +0100, Bartosz Golaszewski wrote:
> On Mon, Nov 10, 2025 at 10:02 AM Philipp Zabel <p.zabel@pengutronix.de> wrote:
> >
> > On Do, 2025-11-06 at 15:32 +0100, Bartosz Golaszewski wrote:
> > > NOTE: I've picked up commit e5d527be7e69 ("gpio: swnode: don't use the
> > > swnode's name as the key for GPIO lookup") into my fixes branch and will
> > > send it upstream by the end of this week. It will be part of v6.18-rc5
> > > which tag will need to be the base for the future immutable branch
> > > created by Philipp.
> > >
> > > Software node maintainers: if this versions is good to go, can you leave
> > > your Acks under patches 1-3 and allow Philipp to take it through the
> > > reset tree, provided he creates an immutable branch you can pull from
> > > for v6.19?
> >
> > Now that -rc5 is out, could I get an Ack to create an immutable branch
> > with this series on top of v6.18-rc5 (and merge it into reset/next)?
> >
>
> Hi Philipp,
>
> I assume the Reviewed-by tags by Andy and Sakari under patches 1-3
> make them good enough to go in?
I assumed I also need an Acked-by by Greg or Rafael.
regards
Philipp
next prev parent reply other threads:[~2025-11-13 10:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 14:32 [PATCH v6 0/8] reset: rework reset-gpios handling Bartosz Golaszewski
2025-11-06 14:32 ` [PATCH v6 1/8] software node: read the reference args via the fwnode API Bartosz Golaszewski
2025-11-06 14:32 ` [PATCH v6 2/8] software node: increase the reference of the swnode by its fwnode Bartosz Golaszewski
2025-11-06 14:32 ` [PATCH v6 3/8] software node: allow referencing firmware nodes Bartosz Golaszewski
2025-11-06 14:32 ` [PATCH v6 4/8] gpio: swnode: allow referencing GPIO chips by " Bartosz Golaszewski
2025-11-06 14:32 ` [PATCH v6 5/8] reset: order includes alphabetically in reset/core.c Bartosz Golaszewski
2025-11-06 14:32 ` [PATCH v6 6/8] reset: make the provider of reset-gpios the parent of the reset device Bartosz Golaszewski
2025-11-06 14:32 ` [PATCH v6 7/8] reset: gpio: convert the driver to using the auxiliary bus Bartosz Golaszewski
2025-11-06 14:32 ` [PATCH v6 8/8] reset: gpio: use software nodes to setup the GPIO lookup Bartosz Golaszewski
2025-11-18 16:44 ` Philipp Zabel
2025-11-18 17:08 ` Bartosz Golaszewski
2025-11-18 18:09 ` Andy Shevchenko
2025-11-19 8:19 ` Philipp Zabel
2025-11-19 8:28 ` Bartosz Golaszewski
2025-11-19 8:41 ` Philipp Zabel
2025-11-10 9:02 ` [PATCH v6 0/8] reset: rework reset-gpios handling Philipp Zabel
2025-11-10 16:57 ` Bartosz Golaszewski
2025-11-13 10:30 ` Philipp Zabel [this message]
2025-11-13 12:16 ` Bartosz Golaszewski
2025-11-13 12:39 ` Bartosz Golaszewski
2025-11-18 11:12 ` Greg Kroah-Hartman
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=7aa5a0ce599f86cc29e5075aa4e35155dfcd013e.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=dakr@kernel.org \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).