linux-kernel - Re: [PATCH RFC] kunit: respect KBUILD

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: <CAHMDPKXwtOLuM9Qj2AMcjoMGe8JbBFgLAOgyqg1UpCgxArEGmg@mail.gmail.com>
Date: Tue, 6 Jan 2026 01:29:45 +0900
From: Ryota Sakamoto <sakamo.ryota@...il.com>
To: David Gow <davidgow@...gle.com>
Cc: Brendan Higgins <brendan.higgins@...ux.dev>, Rae Moar <raemoar63@...il.com>, 
	linux-kselftest@...r.kernel.org, kunit-dev@...glegroups.com, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC] kunit: respect KBUILD_OUTPUT env variable by default

Hi David,
Thank you for your review.

On Mon, Jan 5, 2026 at 5:53 PM David Gow <davidgow@...gle.com> wrote:
> Two small thoughts:
> - Do we want to make KBUILD_OUTPUT the KUnit output directory
> directly, rather than nesting .kunit?
> - Do we want to make the --build_dir option relative to KBUILD_OUTPUT,
> instead of the current directory?
>
> Personally, I think the answer to both of those is probably no, so I'm
> happy to take this as-is.

I agree with you that the answer for both points is no. Keeping the nesting in
KBUILD_OUTPUT seems cleaner, and keeping --build_dir explicit avoids confusion.

I will send v2 shortly with the Reviewed-by tag and remove RFC.

Regards,