linux-kernel - Re: linux-next: duplicate patches in the opp 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]

Date: Thu, 14 Mar 2024 10:02:32 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: 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 opp tree

On 14-03-24, 08:43, Stephen Rothwell wrote:
> Hi all,
> 
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
> 
>   0b5466a8bc71 ("OPP: Extend dev_pm_opp_data with turbo support")
>   3678779d8b64 ("OPP: debugfs: Fix warning with W=1 builds")
>   6c9a1a56d316 ("OPP: debugfs: Fix warning around icc_get_name()")
>   ace4b31b297d ("cpufreq: Move dev_pm_opp_{init|free}_cpufreq_table() to pm_opp.h")
>   bde3127675ff ("dt-bindings: opp: drop maxItems from inner items")

Hi Stephen,

Sorry about that. While creating the tag for the pull request, I
rebased the commits and forgot to push my branch again. Done now.
Should match Linus's tree now.

-- 
viresh