From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Konstantin Khlebnikov" <koct9i@gmail.com>,
"Stephen Boyd" <swboyd@chromium.org>,
"Sasha Levin" <sashal@kernel.org>,
"Alexis Lothoré" <alexis.lothore@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
linux-kernel@vger.kernel.org,
"Luca Ceresoli" <luca.ceresoli@bootlin.com>
Subject: Re: [PATCH 0/3] scripts/decode_stacktrace.sh: improve error reporting and usability
Date: Mon, 22 Apr 2024 11:42:46 +0200 [thread overview]
Message-ID: <20240422114246.5320a638@booty> (raw)
In-Reply-To: <20240311-decode_stacktrace-find_module-improvements-v1-0-8bea42b421aa@bootlin.com>
Hello,
On Mon, 11 Mar 2024 16:24:53 +0100
Luca Ceresoli <luca.ceresoli@bootlin.com> wrote:
> This small series improves usability of scripts/decode_stacktrace.sh by
> improving the usage text and correctly reporting when modules are built
> without debugging symbols.
>
> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Gently pinging about this series.
Best regards,
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-04-22 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 15:24 [PATCH 0/3] scripts/decode_stacktrace.sh: improve error reporting and usability Luca Ceresoli
2024-03-11 15:24 ` [PATCH 1/3] scripts/decode_stacktrace.sh: remove find_module recursion and improve error reporting Luca Ceresoli
2024-05-08 21:35 ` Stephen Boyd
2024-05-09 8:16 ` Luca Ceresoli
2024-03-11 15:24 ` [PATCH 2/3] scripts/decode_stacktrace.sh: clarify command line Luca Ceresoli
2024-05-08 21:37 ` Stephen Boyd
2024-03-11 15:24 ` [PATCH 3/3] scripts/decode_stacktrace.sh: add '-h' flag Luca Ceresoli
2024-05-08 21:38 ` Stephen Boyd
2024-04-22 9:42 ` Luca Ceresoli [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=20240422114246.5320a638@booty \
--to=luca.ceresoli@bootlin.com \
--cc=alexis.lothore@bootlin.com \
--cc=koct9i@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=swboyd@chromium.org \
--cc=thomas.petazzoni@bootlin.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