From: Philipp Zabel <p.zabel@pengutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: Nishanth Menon <nm@ti.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Tero Kristo <kristo@kernel.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Kevin Hilman <khilman@baylibre.com>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
Santosh Shilimkar <ssantosh@kernel.org>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH 0/3] reset: Convert to platform remove callback returning void
Date: Mon, 27 May 2024 09:23:48 +0200 [thread overview]
Message-ID: <9b7e1a88a812f5c86ada75b094c95b9cf65891c3.camel@pengutronix.de> (raw)
In-Reply-To: <3emqw7comsegnkso6o3srb3ebeoa7n2m5ckv2ycznu6muh7ydz@krrx33tn4vyv>
Hi Uwe,
On Sa, 2024-05-25 at 12:14 +0200, Uwe Kleine-König wrote:
> Hello Philipp,
>
> On Tue, Mar 12, 2024 at 09:47:24AM +0100, Philipp Zabel wrote:
> > On Di, 2024-03-05 at 22:32 +0100, Uwe Kleine-König wrote:
> > > this series converts all platform drivers below drivers/reset to struct
> > > platform_driver::remove_new(). See commit 5c5a7680e67b ("platform:
> > > Provide a remove callback that returns no value") for an extended
> > > explanation and the eventual goal.
> > >
> > > All conversations are trivial, because their .remove() callbacks
> > > returned zero unconditionally.
> > >
> > > There are no interdependencies between these patches, so they could be
> > > picked up individually. But I'd hope that they get picked up all
> > > together by Philipp.
> >
> > Thank you, I'll pick them up.
> >
> > Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
>
> These patches made it into next (as v6.9-rc1..6d89df61650d), but not yet
> into Linus's tree for v6.10-rc1. I intend to send a PR to Greg early next week changing
> platform_driver::remove to match remove_new to cook
> long in next for v6.11-rc1. If these reset commits don't make it in in time,
> I'll be so bold and just include the commits from your for-next branch
> in my PR.
Please do, thank you.
Acked-by: Philipp Zabel <p.zabel@pengutronix.de>
regards
Philipp
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2024-05-27 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 21:32 [PATCH 0/3] reset: Convert to platform remove callback returning void Uwe Kleine-König
2024-03-05 21:32 ` [PATCH 1/3] reset: meson-audio-arb: " Uwe Kleine-König
2024-03-12 8:47 ` [PATCH 0/3] reset: " Philipp Zabel
2024-05-25 10:14 ` Uwe Kleine-König
2024-05-27 7:23 ` Philipp Zabel [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=9b7e1a88a812f5c86ada75b094c95b9cf65891c3.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=kernel@pengutronix.de \
--cc=khilman@baylibre.com \
--cc=kristo@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=nm@ti.com \
--cc=ssantosh@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).