linux-kernel - Re: [PATCH v2] .gitignore: ignore compile

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEf4Bzb4gDq1Erj6m1tjZCUqasCEb+BH_M-73u0L6uVdohL7yw@mail.gmail.com>
Date: Tue, 12 Aug 2025 15:22:35 -0700
From: Andrii Nakryiko <andrii.nakryiko@...il.com>
To: Nathan Chancellor <nathan@...nel.org>
Cc: masahiroy@...nel.org, Andrii Nakryiko <andrii@...nel.org>, linux-kernel@...r.kernel.org, 
	Miguel Ojeda <miguel.ojeda.sandonis@...il.com>, ojeda@...nel.org, bpf@...r.kernel.org, 
	kernel-team@...a.com, linux-pm@...r.kernel.org, 
	Eduard Zingerman <eddyz87@...il.com>, Nicolas Schier <nsc@...nel.org>
Subject: Re: [PATCH v2] .gitignore: ignore compile_commands.json globally

On Tue, Aug 12, 2025 at 3:14 PM Nathan Chancellor <nathan@...nel.org> wrote:
>
> Hi Andrii,
>
> On Tue, Aug 12, 2025 at 02:55:22PM -0700, Andrii Nakryiko wrote:
> > Seems like this has fallen through the cracks... I guess we can take
> > it through the bpf-next tree, if there is no better home for this?
>
> Masahiro recently turned over maintenance of the Kbuild build tree as of
> commit 8d6841d5cb20 ("MAINTAINERS: hand over Kbuild maintenance"). I am
> happy to pick this up in the new Kbuild tree but I have no objections to
> you taking it via BPF with
>
>   Acked-by: Nathan Chancellor <nathan@...nel.org>
>
> if you would like to. I suspect it matters most to the BPF folks anyways.

I think the Kbuild tree makes most sense, as there is nothing BPF
specific here. I'm just carrying my custom compile_commands.json for
libbpf project and being careful about not accidentally committing it
(so far I managed), so I only want this to *eventually* make its way
into the kernel repo. Not urgent, though.

Please take it through the Kbuild tree then, thanks!

>
> Cheers,
> Nathan