linux-kernel - Re: [PATCHv2] Documentation: kgdb: Replace deprecated remotebaud

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87ee5kpki1.fsf@meer.lwn.net>
Date:   Thu, 06 Jan 2022 15:28:06 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Christian Löhle <CLoehle@...erstone.com>,
        "jason.wessel@...driver.com" <jason.wessel@...driver.com>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "daniel.thompson@...aro.org" <daniel.thompson@...aro.org>
Cc:     "dianders@...omium.org" <dianders@...omium.org>
Subject: Re: [PATCHv2] Documentation: kgdb: Replace deprecated remotebaud

Christian Löhle <CLoehle@...erstone.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@...erstone.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