linux-kernel - Re: linux-next: build failure after merge of the block 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: <874iodtshv.fsf@t14s.mail-host-address-is-not-set>
Date: Thu, 22 Jan 2026 19:25:00 +0100
From: Andreas Hindborg <a.hindborg@...nel.org>
To: Mark Brown <broonie@...nel.org>, Miguel Ojeda
 <miguel.ojeda.sandonis@...il.com>
Cc: David Gow <davidgow@...gle.com>, Tamir Duberstein <tamird@...il.com>, Jens
 Axboe <axboe@...nel.dk>, Miguel Ojeda <ojeda@...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 block tree

"Mark Brown" <broonie@...nel.org> writes:

> On Wed, Jan 21, 2026 at 07:55:39PM +0100, Miguel Ojeda wrote:
>> On Wed, Jan 21, 2026 at 3:56 PM Mark Brown <broonie@...nel.org> wrote:
>
>> > We do really want things to respect O=, all the -next builds are using
>> > that, so if anything shows up in the source tree that's a concern.  I am
>> > bodging that for the kselftest build at the minute but it's not great.
>
>> Not sure what you mean about `O=`. Using `O=` is supported (both for
>> the subdir and external dir cases which are slightly different in the
>> build system). Modulo bugs, of course.
>
>> If you mean to ask whether `rustfmt` creates files: no, it replaces
>> in-place, i.e. by `git status` I meant you would see modified files,
>> not new ones.
>
> I was asking because you were mentioning checking git status and since
> we are doing out of tree builds there should be nothing changing in the
> source at all.  I think with the way we get trees to the build machine
> it won't make a difference in the end though if no new files are
> created so it'll actually be fine...

The `rustfmt` target will change the source directory even when building
with `O=...`, if it decides formatting changes are required.


Best regards,
Andreas Hindborg