From: Matthieu Baerts <matttbe@kernel.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: akpm@linux-foundation.org, luca.ceresoli@bootlin.com,
cmllamas@google.com, mhiramat@kernel.org,
linux-kernel@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] scripts: Getting rid of -h option, when empty, the usage will be shown
Date: Thu, 11 Jun 2026 15:41:54 +0200 [thread overview]
Message-ID: <2f655801-5824-4943-8455-c63ebfca7c49@kernel.org> (raw)
In-Reply-To: <20260607232509.2812679-1-unixbhaskar@gmail.com>
Hi Bhaskar,
On 08/06/2026 01:20, Bhaskar Chowdhury wrote:
> cc:sashal@kernel.org
Sasha was not in Cc. You need you write "Cc: ..." instead for
git-send-email to add someone in Cc
> Make thing simple to show the help/usage info, when no argument given.
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> scripts/decode_stacktrace.sh | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/scripts/decode_stacktrace.sh b/scripts/decode_stacktrace.sh
> index 39d60d477bf3..fa084f128802 100755
> --- a/scripts/decode_stacktrace.sh
> +++ b/scripts/decode_stacktrace.sh
> @@ -7,7 +7,6 @@ usage() {
> echo "Usage:"
> echo " $0 [-R] -r <release>"
> echo " $0 [-R] [<vmlinux> [<base_path>|auto [<modules_path>]]]"
As mentioned on this line above, this script can be called without any
argument.
So, if I'm not mistaken, the modification you are suggesting here cannot
be accepted.
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-06-11 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 23:20 Bhaskar Chowdhury
2026-06-11 13:41 ` Matthieu Baerts [this message]
[not found] ` <20260613233012.3245472-2-unixbhaskar@gmail.com>
2026-06-13 23:24 ` Bhaskar Chowdhury
2026-06-17 14:18 ` Sasha Levin
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=2f655801-5824-4943-8455-c63ebfca7c49@kernel.org \
--to=matttbe@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cmllamas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=mhiramat@kernel.org \
--cc=sashal@kernel.org \
--cc=unixbhaskar@gmail.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