From: Nir Lichtman <nir@lichtman.org>
To: jason.wessel@windriver.com, daniel.thompson@linaro.org,
dianders@chromium.org, linux-kernel@vger.kernel.org
Subject: [PATCH] kdb: Fix incomplete usage help of md, mds and btc commands
Date: Thu, 31 Oct 2024 20:40:41 +0000 [thread overview]
Message-ID: <20241031204041.GA27585@lichtman.org> (raw)
Fix kdb usage help to document some currently missing CLI commands options
Signed-off-by: Nir Lichtman <nir@lichtman.org>
---
kernel/debug/kdb/kdb_main.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/kernel/debug/kdb/kdb_main.c b/kernel/debug/kdb/kdb_main.c
index f5f7d7fb5936..0bdffb17b163 100644
--- a/kernel/debug/kdb/kdb_main.c
+++ b/kernel/debug/kdb/kdb_main.c
@@ -2667,7 +2667,7 @@ EXPORT_SYMBOL_GPL(kdb_unregister);
static kdbtab_t maintab[] = {
{ .name = "md",
.func = kdb_md,
- .usage = "<vaddr>",
+ .usage = "<vaddr> [lines] [radix]",
.help = "Display Memory Contents, also mdWcN, e.g. md8c1",
.minlen = 1,
.flags = KDB_ENABLE_MEM_READ | KDB_REPEAT_NO_ARGS,
@@ -2686,7 +2686,7 @@ static kdbtab_t maintab[] = {
},
{ .name = "mds",
.func = kdb_md,
- .usage = "<vaddr>",
+ .usage = "<vaddr> [lines] [radix]",
.help = "Display Memory Symbolically",
.flags = KDB_ENABLE_MEM_READ | KDB_REPEAT_NO_ARGS,
},
@@ -2743,8 +2743,8 @@ static kdbtab_t maintab[] = {
},
{ .name = "btc",
.func = kdb_bt,
- .usage = "",
- .help = "Backtrace current process on each cpu",
+ .usage = "[<cpu>]",
+ .help = "Backtrace current process on each cpu, or a specific one if cpu is passed",
.flags = KDB_ENABLE_INSPECT,
},
{ .name = "btt",
--
2.39.2
next reply other threads:[~2024-10-31 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 20:40 Nir Lichtman [this message]
2024-11-01 15:42 ` [PATCH] kdb: Fix incomplete usage help of md, mds and btc commands Doug Anderson
2024-11-02 20:31 ` Nir Lichtman
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=20241031204041.GA27585@lichtman.org \
--to=nir@lichtman.org \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox