linux-kernel - Re: linux-next: duplicate patches in the clk tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20240423125011.tjyvkzns7fqpdsl2@bogus>
Date: Tue, 23 Apr 2024 13:50:11 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Mike Turquette <mturquette@...libre.com>,
	Stephen Boyd <sboyd@...nel.org>,
	Sudeep Holla <sudeep.holla@....com>,
	Cristian Marussi <cristian.marussi@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patches in the clk tree

On Tue, Apr 23, 2024 at 10:39:34AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> The following commits are also in the scmi tree as different commits
> (but the same patches):
> 
>   87af9481af53 ("clk: scmi: Add support for get/set duty_cycle operations")
>   fa23e091236b ("clk: scmi: Add support for re-parenting restricted clocks")
>   c3ad1d0a7ef2 ("clk: scmi: Add support for rate change restricted clocks")
>   a1b8faf8784c ("clk: scmi: Add support for state control restricted clocks")
>   2641ee13c449 ("clk: scmi: Allocate CLK operations dynamically")
> 
> These are commits
> 
>   ca82ded0e3dc ("clk: scmi: Add support for get/set duty_cycle operations")
>   3a0501ad6fd4 ("clk: scmi: Add support for re-parenting restricted clocks")
>   4562172e3ec2 ("clk: scmi: Add support for rate change restricted clocks")
>   6785c6c261bd ("clk: scmi: Add support for state control restricted clocks")
>   4196d89b2393 ("clk: scmi: Allocate CLK operations dynamically")
> 
> in the scmi tree.

I will drop them from the scmi tree.


-- 
Regards,
Sudeep