linux-kernel - Re: [PATCH 08/23] kbuild: simplify find command for rustfmt

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: <CANiq72nPAn1HWwHBL9qFw=V-BY1F3ckgmkb7c23vfKuH-oB9Qg@mail.gmail.com>
Date: Mon, 30 Sep 2024 20:37:49 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: linux-kbuild@...r.kernel.org, Miguel Ojeda <ojeda@...nel.org>, 
	rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nicolas@...sle.eu>
Subject: Re: [PATCH 08/23] kbuild: simplify find command for rustfmt

On Tue, Sep 17, 2024 at 4:17 PM Masahiro Yamada <masahiroy@...nel.org> wrote:
>
> The correct use of the -prune option can be seen in the 'make clean'
> rule.

Yeah, this `-prune` should not have been like that -- sorry about that.

The comment above this recipe should be updated.

I am not sure I understand the part of the commit message about the
rust/test change. Do you mean that we should use `srctree` in case
there is a stale one in the source tree from a previous
non-completely-clean in-source-tree build? I think the original
intention was to skip the objtree one if it were a subdir of srctree
(and that is why the use of absolute paths).

Although I think we can simplify further by just removing the logic
about `rust/test`, since we don't generate `*.rs` files there anyway
at the moment.

Cheers,
Miguel