From: Uday Shankar <ushankar@purestorage.com>
To: Steven Rostedt <rostedt@goodmis.org>,
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>
Cc: linux-trace-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Uday Shankar <ushankar@purestorage.com>
Subject: [PATCH 0/2] kbuild: rpm-pkg: improve debuggability
Date: Mon, 10 Feb 2025 18:11:53 -0700 [thread overview]
Message-ID: <20250210-debuginfo-v1-0-368feb58292a@purestorage.com> (raw)
This patch set aims to improve debuggability of kernels packaged using
the rpm-pkg target by producing debuginfo and debugsource RPMs that
contain a full set of debugging information for the kernel. The
preexisting kernel-%{KERNELRELEASE} RPM is also shrunk by moving all
debuginfo out of it into the new debuginfo RPM.
The first patch is just a bit of cleanup to keep rpmbuild happy, and the
second patch contains the main work.
This is technically a v2 for the following patch, but since it's been a
while I didn't mark it as such
https://lore.kernel.org/linux-kbuild/20240910014327.1726214-1-ushankar@purestorage.com/
Signed-off-by: Uday Shankar <ushankar@purestorage.com>
---
Uday Shankar (2):
scripts: make python shebangs specific about desired version
kbuild: rpm-pkg: build debuginfo and debugsource RPMs
scripts/package/kernel.spec | 31 +++++++++++++++++++++++++++++--
scripts/package/mkspec | 3 +++
scripts/show_delta | 2 +-
scripts/tracing/draw_functrace.py | 2 +-
4 files changed, 34 insertions(+), 4 deletions(-)
---
base-commit: a64dcfb451e254085a7daee5fe51bf22959d52d3
change-id: 20250209-debuginfo-cd3d9417af21
Best regards,
--
Uday Shankar <ushankar@purestorage.com>
next reply other threads:[~2025-02-11 1:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 1:11 Uday Shankar [this message]
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
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=20250210-debuginfo-v1-0-368feb58292a@purestorage.com \
--to=ushankar@purestorage.com \
--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=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.