public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: nick black <dankamongmen@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] serial-console.rst: break up code chunks
Date: Fri, 20 Aug 2021 08:11:18 +0200	[thread overview]
Message-ID: <YR9HhhyDc9bjfQoh@ada.ifak-system.com> (raw)
In-Reply-To: <YR1KmVfEmAZVGXIE@schwarzgerat.orthanc>

Hello,

Am Wed, Aug 18, 2021 at 01:59:53PM -0400 schrieb nick black:
> Trivial: there are two code sections here, not one.
> Break up the RST backticks.
> 
> Signed-off-by: Nick Black <dankamongmen@gmail.com>
> 
> ---
>  Documentation/admin-guide/serial-console.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git Documentation/admin-guide/serial-console.rst Documentation/admin-guide/serial-console.rst
> index a8d1e36b627a..b8c803afae2f 100644
> --- Documentation/admin-guide/serial-console.rst
> +++ Documentation/admin-guide/serial-console.rst
> @@ -96,7 +96,7 @@ Replace the sample values as needed.
>     open ``/dev/console``. If you have created the new ``/dev/console`` device,
>     and your console is NOT the virtual console some programs will fail.
>     Those are programs that want to access the VT interface, and use
> -   ``/dev/console instead of /dev/tty0``. Some of those programs are::
> +   ``/dev/console`` instead of ``/dev/tty0``. Some of those programs are::
>  
>       Xfree86, svgalib, gpm, SVGATextMode

Reviewed-by: Alexander Dahl <ada@thorsis.com>

Greets
Alex


      reply	other threads:[~2021-08-20  6:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 17:59 [PATCH] serial-console.rst: break up code chunks nick black
2021-08-20  6:11 ` Alexander Dahl [this message]

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=YR9HhhyDc9bjfQoh@ada.ifak-system.com \
    --to=ada@thorsis.com \
    --cc=dankamongmen@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=mchehab+huawei@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