linux-kernel - Re: linux-next: build failure after merge of the rust-pin-init 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: <CANiq72kowA0oNZQYLnQBZfgm2caS+3Fmq7h0jPT2RF68Fjgiaw@mail.gmail.com>
Date: Tue, 10 Jun 2025 11:56:30 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Benno Lossin <lossin@...nel.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Miguel Ojeda <ojeda@...nel.org>, 
	Andreas Hindborg <a.hindborg@...nel.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the rust-pin-init tree

On Tue, Jun 10, 2025 at 10:15 AM Benno Lossin <lossin@...nel.org> wrote:
>
> @Miguel, @Andreas, how should I go about this? Send the commit above
> augmented with the diff, or send a patch with just the diff to the list?
> Or apply the diff directly to the commit in the pin-init-next branch &
> rebasing (potentially adding an Acked-by from Andreas)? Or some other
> way?

If I understand correctly, the commit that introduced the issue
(0bcaea04244b) is in your branch (rust/pin-init-next), thus you should
fix it in your branch.

Personally, I would just rebase, since you just applied them hours ago.

As a maintainer, you are trusted to not introduce a change that others
could disagree with (especially on their files) -- but you already
told Andreas and discussed it here, so you did the right thing :)

You can consider mentioning the change in the [ ... ] part, if you want.

Thanks!

Cheers,
Miguel