All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Brian Masney <bmasney@redhat.com>
Cc: Maxime Ripard <mripard@kernel.org>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Alchemy: convert from round_rate() to determine_rate()
Date: Fri, 29 Aug 2025 12:22:40 +0200	[thread overview]
Message-ID: <aLF_cFrbfaouDQ8O@alpha.franken.de> (raw)
In-Reply-To: <20250810-mips-round-rate-v1-1-54e424c520dd@redhat.com>

On Sun, Aug 10, 2025 at 06:30:23PM -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.
> 
> Note that prior to running Coccinelle, alchemy_clk_aux_roundr() was
> renamed to alchemy_clk_aux_round_rate(). A few minor style cleanups
> were also done by hand.
> 
> Signed-off-by: Brian Masney <bmasney@redhat.com>
> ---
> [...]
> https://lore.kernel.org/cocci/67642477-5f3e-4b2a-914d-579a54f48cbd@intel.com/
> ---
>  arch/mips/alchemy/common/clock.c | 18 +++++++++++-------
>  1 file changed, 11 insertions(+), 7 deletions(-)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2025-08-29 10:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-10 22:30 [PATCH] MIPS: Alchemy: convert from round_rate() to determine_rate() Brian Masney
2025-08-11  7:50 ` Manuel Lauss
2025-08-29 10:22 ` Thomas Bogendoerfer [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=aLF_cFrbfaouDQ8O@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=bmasney@redhat.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=mripard@kernel.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 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.