[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250501132211.0310ae49@donnerap.manchester.arm.com>
Date: Thu, 1 May 2025 13:22:11 +0100
From: Andre Przywara <andre.przywara@....com>
To: Chen-Yu Tsai <wens@...e.org>
Cc: Michael Turquette <mturquette@...libre.com>, Stephen Boyd
<sboyd@...nel.org>, Jernej Skrabec <jernej.skrabec@...il.com>, Samuel
Holland <samuel@...lland.org>, <linux-clk@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <linux-sunxi@...ts.linux.dev>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] clk: sunxi-ng: fix order of arguments in clock macro
On Thu, 1 May 2025 20:14:24 +0800
Chen-Yu Tsai <wens@...e.org> wrote:
Hi,
> On Wed, 30 Apr 2025 10:53:25 +0100, Andre Przywara wrote:
> > When introducing the SUNXI_CCU_MP_DATA_WITH_MUX_GATE_FEAT macro, the order
> > of the last two arguments was different between the users and the
> > definition: features became flags and flags became features.
> >
> > This just didn't end up in a desaster yet because most users ended up
> > passing 0 for both arguments, and other clocks (for the new A523 SoC) are
> > not yet used.
> >
> > [...]
>
> Applied to clk-fixes-for-6.15 in git@...hub.com:linux-sunxi/linux-sunxi.git, thanks!
thanks for that, but the URL here is not correct, is it? Should be the
kernel.org repo instead? Saw this already in other "applied" emails.
Cheers,
Andre
>
> [1/1] clk: sunxi-ng: fix order of arguments in clock macro
> commit: 4a9c3c3215491f25bc66d615faa921c814b1a479
>
> Best regards,
Powered by blists - more mailing lists