linux-kernel - Re: linux-next: duplicate patch in the rust 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANiq72kHWgsvmxPYSAHpM5HaxCSf73t4NkPsBRXiPMTTe_u51w@mail.gmail.com>
Date: Mon, 20 Oct 2025 04:14:31 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Miguel Ojeda <ojeda@...nel.org>, Greg KH <greg@...ah.com>, Arnd Bergmann <arnd@...db.de>, 
	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 rust tree

On Mon, Oct 20, 2025 at 3:39 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> The following commit is also in the char-misc.curent tree as a different
> commit (but the same patch):
>
>   abae8f3c8374 ("[TEMPORARY] rust_binder: clean `clippy::mem_replace_with_default` warning")
>
> This is commit
>
>   7e69a24b6b35 ("rust_binder: clean `clippy::mem_replace_with_default` warning")
>
> in the char-misc.current tree.

Yeah, I added it at the top to be able to have the `rust-next`
Clippy-clean, but I don't plan to submit it.

Since you detect them, I will remove it to avoid confusion.

Greg: it would be nice to get that one submitted to Linus during the
-rcs, rather than the next merge window.

Thanks!

Cheers,
Miguel