From: Randy Dunlap <rdunlap@infradead.org>
To: Zenghui Yu <zenghui.yu@linux.dev>,
kgdb-bugreport@lists.sourceforge.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: jason.wessel@windriver.com, danielt@kernel.org,
dianders@chromium.org, corbet@lwn.net, skhan@linuxfoundation.org
Subject: Re: [PATCH] docs: kgdb: Fix path of driver options
Date: Sat, 20 Jun 2026 17:09:18 -0700 [thread overview]
Message-ID: <f23bdd14-359b-4533-b062-30d603116caa@infradead.org> (raw)
In-Reply-To: <20260620234035.9917-1-zenghui.yu@linux.dev>
On 6/20/26 4:40 PM, Zenghui Yu wrote:
> The correct path of driver options should be
> /sys/module/<driver>/parameters/<option>. Fix it.
>
> Signed-off-by: Zenghui Yu <zenghui.yu@linux.dev>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> Documentation/process/debugging/kgdb.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/process/debugging/kgdb.rst b/Documentation/process/debugging/kgdb.rst
> index c4d0a9121d52..316b1d74e9c8 100644
> --- a/Documentation/process/debugging/kgdb.rst
> +++ b/Documentation/process/debugging/kgdb.rst
> @@ -513,7 +513,7 @@ unregister all the kernel hook points.
>
> All kgdb I/O drivers can be reconfigured at run time, if
> ``CONFIG_SYSFS`` and ``CONFIG_MODULES`` are enabled, by echo'ing a new
> -config string to ``/sys/module/<driver>/parameter/<option>``. The driver
> +config string to ``/sys/module/<driver>/parameters/<option>``. The driver
> can be unconfigured by passing an empty string. You cannot change the
> configuration while the debugger is attached. Make sure to detach the
> debugger with the ``detach`` command prior to trying to unconfigure a
--
~Randy
next prev parent reply other threads:[~2026-06-21 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 23:40 Zenghui Yu
2026-06-21 0:09 ` Randy Dunlap [this message]
2026-06-24 10:40 ` Daniel Thompson
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=f23bdd14-359b-4533-b062-30d603116caa@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=danielt@kernel.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
--cc=zenghui.yu@linux.dev \
/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
all inboxes | Powered by JetHome®