public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Uday Shankar <ushankar@purestorage.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nicolas Schier <nicolas@fjasle.eu>,
	linux-trace-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 0/2] kbuild: rpm-pkg: improve debuggability
Date: Mon, 3 Mar 2025 22:46:53 -0500	[thread overview]
Message-ID: <20250303224653.3e756252@batman.local.home> (raw)
In-Reply-To: <Z7zwDV5BvezaS6Sn@dev-ushankar.dev.purestorage.com>

On Mon, 24 Feb 2025 15:17:49 -0700
Uday Shankar <ushankar@purestorage.com> wrote:

> On Mon, Feb 24, 2025 at 05:07:09PM -0500, Steven Rostedt wrote:
> > On Mon, 24 Feb 2025 12:35:00 -0700
> > Uday Shankar <ushankar@purestorage.com> wrote:
> >   
> > > On Mon, Feb 17, 2025 at 07:27:06PM -0700, Uday Shankar wrote:  
> > > > ping    
> > > 
> > > ping again  
> > 
> > Do you just package it, or do you actually use it?  
> 
> Are you talking about the two scripts whose shebangs I modified in patch
> 1? Those scripts aren't used by the build process, they're just packaged
> in kernel-devel by the following command
> 
> %{make} %{makeflags} run-command KBUILD_RUN_COMMAND='${srctree}/scripts/package/install-extmod-build %{buildroot}/usr/src/kernels/%{KERNELRELEASE}'
> 
> Presumably those scripts are important to users of kernel-devel, which
> is supposed to "provide kernel headers and makefiles sufficient to build
> modules against the ... kernel." Though looking closer at these scripts,
> they look like they're probably extraneous for that purpose.

Sorry, I missed your reply here.

I'm asking if anyone uses draw_functrace.py or if it can simply be deleted.

The rest of the changes are for the build maintainer not me.

-- Steve

  reply	other threads:[~2025-03-04  3:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-11  1:11 [PATCH 0/2] kbuild: rpm-pkg: improve debuggability Uday Shankar
2025-02-11  1:11 ` [PATCH 1/2] scripts: make python shebangs specific about desired version Uday Shankar
2025-02-18 14:34   ` Steven Rostedt
2025-03-06 17:29   ` Masahiro Yamada
2025-02-11  1:11 ` [PATCH 2/2] kbuild: rpm-pkg: build debuginfo and debugsource RPMs Uday Shankar
2025-03-14 19:56   ` Masahiro Yamada
2025-03-15  1:00     ` Uday Shankar
2025-02-18  2:27 ` [PATCH 0/2] kbuild: rpm-pkg: improve debuggability Uday Shankar
2025-02-24 19:35   ` Uday Shankar
2025-02-24 22:07     ` Steven Rostedt
2025-02-24 22:17       ` Uday Shankar
2025-03-04  3:46         ` Steven Rostedt [this message]
2025-03-04  3:09     ` Uday Shankar
2025-03-04 13:06       ` Nathan Chancellor

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=20250303224653.3e756252@batman.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nicolas@fjasle.eu \
    --cc=ushankar@purestorage.com \
    /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