From: Jonathan Corbet <corbet@lwn.net>
To: "Christian Löhle" <CLoehle@hyperstone.com>,
"jason.wessel@windriver.com" <jason.wessel@windriver.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"daniel.thompson@linaro.org" <daniel.thompson@linaro.org>
Cc: "dianders@chromium.org" <dianders@chromium.org>
Subject: Re: [PATCHv2] Documentation: kgdb: Replace deprecated remotebaud
Date: Thu, 06 Jan 2022 15:28:06 -0700 [thread overview]
Message-ID: <87ee5kpki1.fsf@meer.lwn.net> (raw)
In-Reply-To: <4050689967ed46baaa3bfadda53a0e73@hyperstone.com>
Christian Löhle <CLoehle@hyperstone.com> writes:
> Using set remotebaud to set the baud rate was deprecated in
> gdb-7.7 and completely removed from the command parser in gdb-7.8
> (released in 2014). Adopt set serial baud instead.
>
> Signed-off-by: Christian Loehle <cloehle@hyperstone.com>
> ---
> Documentation/dev-tools/kgdb.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/dev-tools/kgdb.rst b/Documentation/dev-tools/kgdb.rst
> index 43456244651a..7c90e111b364 100644
> --- a/Documentation/dev-tools/kgdb.rst
> +++ b/Documentation/dev-tools/kgdb.rst
> @@ -557,7 +557,7 @@ Connecting with gdb to a serial port
> Example (using a directly connected port)::
>
> % gdb ./vmlinux
> - (gdb) set remotebaud 115200
> + (gdb) set serial baud 115200
> (gdb) target remote /dev/ttyS0
I've applied this, thanks.
I can help but wonder, though, whether the historical information in the
changelog actually belongs in the document itself. A user on some
ancient system who can't make the example work is probably unlikely to
consult the git history when looking for a solution.
jon
next prev parent reply other threads:[~2022-01-06 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 16:56 [PATCH] Documentation: kgdb: Replace deprecated remotebaud Christian Löhle
2022-01-04 17:27 ` Daniel Thompson
2022-01-05 9:58 ` [PATCHv2] " Christian Löhle
2022-01-05 10:52 ` Daniel Thompson
2022-01-06 22:28 ` Jonathan Corbet [this message]
2022-01-10 8:26 ` [PATCHv3] " Christian Löhle
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=87ee5kpki1.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=CLoehle@hyperstone.com \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=linux-doc@vger.kernel.org \
--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 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.