From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Brian Masney <bmasney@redhat.com>,
Iwona Winiarska <iwona.winiarska@intel.com>,
Joel Stanley <joel@jms.id.au>, Maxime Ripard <mripard@kernel.org>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
openbmc@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] peci: controller: peci-aspeed: convert from round_rate() to determine_rate()
Date: Mon, 15 Sep 2025 14:36:48 +0930 [thread overview]
Message-ID: <28dc3bd8aeca7e3164747960747f75060c596704.camel@codeconstruct.com.au> (raw)
In-Reply-To: <aMatZAX6eFI1RmDH@redhat.com>
Hi Brian,
On Sun, 2025-09-14 at 07:56 -0400, Brian Masney wrote:
> Hi Iwona, Joel, and Andrew,
>
> On Sun, Aug 10, 2025 at 06:21:51PM -0400, Brian Masney wrote:
> > The round_rate() clk ops is deprecated, so migrate this driver from
> > round_rate() to determine_rate() using the Coccinelle semantic patch
> > appended to the "under-the-cut" portion of the patch.
> >
> > Signed-off-by: Brian Masney <bmasney@redhat.com>
>
> Would it be possible to get this picked up for v6.18? I'd like to remove
> this API from drivers/clk in v6.19.
My (strong) preference is that Iwona applies it, but I'll keep an eye
out for any unusual delays.
Andrew
next prev parent reply other threads:[~2025-09-15 5:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 22:21 [PATCH] peci: controller: peci-aspeed: convert from round_rate() to determine_rate() Brian Masney
2025-09-14 11:56 ` Brian Masney
2025-09-15 5:06 ` Andrew Jeffery [this message]
2025-10-16 16:11 ` Brian Masney
2025-10-17 6:22 ` Andrew Jeffery
2025-10-17 6:41 ` Greg Kroah-Hartman
2025-10-17 7:27 ` Andrew Jeffery
2025-10-17 7:43 ` Greg Kroah-Hartman
2025-10-19 23:00 ` Andrew Jeffery
2025-10-21 21:01 ` Winiarska, Iwona
2025-10-21 22:35 ` Andrew Jeffery
2025-11-06 23:11 ` Brian Masney
2025-11-14 13:40 ` Winiarska, Iwona
2025-10-21 21:07 ` Winiarska, Iwona
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=28dc3bd8aeca7e3164747960747f75060c596704.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=bmasney@redhat.com \
--cc=iwona.winiarska@intel.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).