From: Nathan Chancellor <nathan@kernel.org>
To: Uday Shankar <ushankar@purestorage.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Masahiro Yamada <masahiroy@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: Tue, 4 Mar 2025 14:06:48 +0100 [thread overview]
Message-ID: <20250304130648.GA3922496@ax162> (raw)
In-Reply-To: <Z8Zu0p2vCAfwXa/L@dev-ushankar.dev.purestorage.com>
Hi Uday,
On Mon, Mar 03, 2025 at 08:09:06PM -0700, Uday Shankar wrote:
> On Mon, Feb 24, 2025 at 12:35:00PM -0700, Uday Shankar wrote:
> > On Mon, Feb 17, 2025 at 07:27:06PM -0700, Uday Shankar wrote:
> > > ping
> >
> > ping again
>
> ping again again. Can someone please take a look at this and/or let me
> know if I'm missing any recipients or if I'm expecting feedback too
> soon?
Your recipients list looks correct to me but I am not super
knowledgeable about the RPM format so I am not sure I can give this a
proper review but I will try to take a look at it when I can find some
time to do some research. Masahiro will be the one to pick this up but
some maintainers are busier than others.
Cheers,
Nathan
prev parent reply other threads:[~2025-03-04 13:06 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
2025-03-04 3:09 ` Uday Shankar
2025-03-04 13:06 ` Nathan Chancellor [this message]
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=20250304130648.GA3922496@ax162 \
--to=nathan@kernel.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=nicolas@fjasle.eu \
--cc=rostedt@goodmis.org \
--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