From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
kernel@pengutronix.de, Maxime Ripard <mripard@kernel.org>
Subject: Re: [PATCH v2] clk: Add a devm variant of clk_rate_exclusive_get()
Date: Tue, 27 Feb 2024 10:31:36 +0000 [thread overview]
Message-ID: <Zd26CLdCCNFtjX+l@shell.armlinux.org.uk> (raw)
In-Reply-To: <n25yhjcopyon7yuo2l6t6akklrfz4l3flcfl34aycdlr7x4yaf@ta53zqedauzo>
On Tue, Feb 27, 2024 at 08:38:54AM +0100, Uwe Kleine-König wrote:
> Hello,
>
> On Thu, Feb 15, 2024 at 10:39:00AM +0100, Uwe Kleine-König wrote:
> > On Thu, Jan 25, 2024 at 10:44:45PM +0100, Uwe Kleine-König wrote:
> > > On Thu, Jan 04, 2024 at 11:55:11PM +0100, Uwe Kleine-König wrote:
> > > > This allows to simplify drivers that use clk_rate_exclusive_get()
> > > > in their probe routine as calling clk_rate_exclusive_put() is cared for
> > > > automatically.
> > > >
> > > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > > ---
> > > > Changes since (implicit) v1, sent with Message-Id:
> > > > 744a6371f94fe96f527eea6e52a600914e6fb6b5.1702403904.git.u.kleine-koenig@pengutronix.de:
> > >
> > > Given that I'm not the only one waiting for this change (see
> > > https://lore.kernel.org/linux-i2c/20240119072223.3986183-1-alexander.stein@ew.tq-group.com)
> > > here comes a gentil ping. It would be great to get this patch into next
> > > now the merge window is closed.
> >
> > Is there a chance to get this into next and then v6.9-rc1?
>
> I wonder if this patch is still on someone's radar and why it wasn't
> applied yet. Does it need an ack by Russell before Stephen picks it up?
> Is it too complicated and needs more time to review? Can someone please
> comment what the stopper is here?
Well, if it does, then the simple way to solve that is:
Acked-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Thanks!
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
WARNING: multiple messages have this Message-ID (diff)
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
kernel@pengutronix.de, Maxime Ripard <mripard@kernel.org>
Subject: Re: [PATCH v2] clk: Add a devm variant of clk_rate_exclusive_get()
Date: Tue, 27 Feb 2024 10:31:36 +0000 [thread overview]
Message-ID: <Zd26CLdCCNFtjX+l@shell.armlinux.org.uk> (raw)
In-Reply-To: <n25yhjcopyon7yuo2l6t6akklrfz4l3flcfl34aycdlr7x4yaf@ta53zqedauzo>
On Tue, Feb 27, 2024 at 08:38:54AM +0100, Uwe Kleine-König wrote:
> Hello,
>
> On Thu, Feb 15, 2024 at 10:39:00AM +0100, Uwe Kleine-König wrote:
> > On Thu, Jan 25, 2024 at 10:44:45PM +0100, Uwe Kleine-König wrote:
> > > On Thu, Jan 04, 2024 at 11:55:11PM +0100, Uwe Kleine-König wrote:
> > > > This allows to simplify drivers that use clk_rate_exclusive_get()
> > > > in their probe routine as calling clk_rate_exclusive_put() is cared for
> > > > automatically.
> > > >
> > > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > > ---
> > > > Changes since (implicit) v1, sent with Message-Id:
> > > > 744a6371f94fe96f527eea6e52a600914e6fb6b5.1702403904.git.u.kleine-koenig@pengutronix.de:
> > >
> > > Given that I'm not the only one waiting for this change (see
> > > https://lore.kernel.org/linux-i2c/20240119072223.3986183-1-alexander.stein@ew.tq-group.com)
> > > here comes a gentil ping. It would be great to get this patch into next
> > > now the merge window is closed.
> >
> > Is there a chance to get this into next and then v6.9-rc1?
>
> I wonder if this patch is still on someone's radar and why it wasn't
> applied yet. Does it need an ack by Russell before Stephen picks it up?
> Is it too complicated and needs more time to review? Can someone please
> comment what the stopper is here?
Well, if it does, then the simple way to solve that is:
Acked-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Thanks!
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-27 10:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 22:55 [PATCH v2] clk: Add a devm variant of clk_rate_exclusive_get() Uwe Kleine-König
2024-01-04 22:55 ` Uwe Kleine-König
2024-01-25 21:44 ` Uwe Kleine-König
2024-01-25 21:44 ` Uwe Kleine-König
2024-02-15 9:39 ` Uwe Kleine-König
2024-02-15 9:39 ` Uwe Kleine-König
2024-02-27 7:38 ` Uwe Kleine-König
2024-02-27 7:38 ` Uwe Kleine-König
2024-02-27 10:31 ` Russell King (Oracle) [this message]
2024-02-27 10:31 ` Russell King (Oracle)
2024-02-29 1:03 ` Stephen Boyd
2024-02-29 1:03 ` Stephen Boyd
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=Zd26CLdCCNFtjX+l@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.