linux-kernel - Re: linux-next: duplicate patch in the mux 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: <133f3d1c-19b2-db19-f4df-c67d1f57b946@axentia.se>
Date: Mon, 13 Jan 2025 09:53:24 +0100
From: Peter Rosin <peda@...ntia.se>
To: Greg KH <greg@...ah.com>, 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 patch in the mux tree

Hi Greg!

2025-01-13 at 06:20, Greg KH wrote:
> [You don't often get email from greg@...ah.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> On Mon, Jan 13, 2025 at 02:26:40PM +1100, Stephen Rothwell wrote:
>> Hi all,
>>
>> The following commit is also in the driver-core tree as a different commit
>> (but the same patch):
>>
>>   49a9b01803e4 ("mux: constify mux class")
>>
>> This is commit
>>
>>   7685ad5f08d9 ("mux: constify mux class")
>>
>> in the driver-core tree.
> 
> Thanks, this should be fine, I thought no one had picked it up :(

It all my fault. Sorry for being unresponsive and thanks for picking
the patch. I have now removed the patch from my mux for-next branch.

Cheers,
Peter