From: "Michal Suchánek" <msuchanek@suse.de>
To: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: "Nathan Chancellor" <nathan@kernel.org>,
linux-kbuild@vger.kernel.org, "Nicolas Schier" <nsc@kernel.org>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Tamir Duberstein" <tamird@kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, "Jiri Slaby" <jslaby@suse.cz>
Subject: Re: [PATCH] kbuild: only clean objtool on mrproper
Date: Tue, 3 Mar 2026 17:22:15 +0100 [thread overview]
Message-ID: <aacKt_BSdCvQZ1BA@kitsune.suse.cz> (raw)
In-Reply-To: <vvccmql35pwtm7lga43lvrlumklddxxahb3c2hfwt4qyqsilhz@g3t7ce3gyyg2>
On Wed, Feb 25, 2026 at 12:37:58PM -0800, Josh Poimboeuf wrote:
> On Wed, Feb 25, 2026 at 09:23:09PM +0100, Michal Suchánek wrote:
> > On Wed, Feb 25, 2026 at 01:04:17PM -0700, Nathan Chancellor wrote:
> > > On Wed, Feb 25, 2026 at 12:26:29PM +0100, Michal Suchanek wrote:
> > > > For packaging purposes I want to be able to grab the tool binaries
> > > > without the .o files
> > > >
> > > > Fixes: 68b4fe32d737 ("kbuild: Add objtool to top-level clean target")
> > > > Signed-off-by: Michal Suchanek <msuchanek@suse.de>
> > >
> > > Wouldn't resolve_btfids need the same treatment?
> >
> > No, make clean runs the clean target for resolve_btfids but the tool
> > remains.
> >
> > > Why is objtool special here?
> >
> > That's what I would like to know as well.
> >
> > > Also, what's the use case? Running 'make clean' then copying what
> > > is left?
> >
> > Yes, that's what my build script has been doing for at least a decade,
> > possibly mutiple decades when it was somebody else's build script.
>
> Why is the build script doing that?
To clollect the generated files, primarily for building modules.
Thanks
Michal
next prev parent reply other threads:[~2026-03-03 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 11:26 [PATCH] kbuild: only clean objtool on mrproper Michal Suchanek
2026-02-25 20:04 ` Nathan Chancellor
2026-02-25 20:23 ` Michal Suchánek
2026-02-25 20:37 ` Josh Poimboeuf
2026-03-03 16:22 ` Michal Suchánek [this message]
2026-02-25 21:21 ` Nathan Chancellor
2026-02-28 5:53 ` Nathan Chancellor
2026-03-03 16:27 ` Michal Suchánek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aacKt_BSdCvQZ1BA@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=jpoimboe@kernel.org \
--cc=jslaby@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tamird@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox