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>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH RESEND v2 0/3] scripts/decode_stacktrace.sh: improve error reporting and usability
Date: Fri, 23 Aug 2024 10:35:54 +0200 [thread overview]
Message-ID: <20240823103554.3d9b77c6@booty> (raw)
In-Reply-To: <20240823-decode_stacktrace-find_module-improvements-v2-0-d7a57d35558b@bootlin.com>
Hello,
On Fri, 23 Aug 2024 10:27:41 +0200
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>
Initial submission of v2, May 2024:
https://lore.kernel.org/all/20240509-decode_stacktrace-find_module-improvements-v2-0-887fb6d5acb9@bootlin.com/
Had no replies, assuming it got forgotten.
Best regards,
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-08-23 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 8:27 [PATCH RESEND v2 0/3] scripts/decode_stacktrace.sh: improve error reporting and usability Luca Ceresoli
2024-08-23 8:27 ` [PATCH RESEND v2 1/3] scripts/decode_stacktrace.sh: remove find_module recursion and improve error reporting Luca Ceresoli
2024-08-23 8:27 ` [PATCH RESEND v2 2/3] scripts/decode_stacktrace.sh: clarify command line Luca Ceresoli
2024-08-23 8:27 ` [PATCH RESEND v2 3/3] scripts/decode_stacktrace.sh: add '-h' flag Luca Ceresoli
2024-08-23 8:35 ` 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=20240823103554.3d9b77c6@booty \
--to=luca.ceresoli@bootlin.com \
--cc=akpm@linux-foundation.org \
--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 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.