From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Colin Ian King <colin.i.king@googlemail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] speakup: Fix typo in documentation "boo" -> "boot"
Date: Thu, 28 Oct 2021 20:24:51 +0200 [thread overview]
Message-ID: <20211028182451.baizgvczghh37zfl@begin> (raw)
In-Reply-To: <20211028182319.613315-1-colin.i.king@gmail.com>
Colin Ian King, le jeu. 28 oct. 2021 19:23:19 +0100, a ecrit:
> There is a typo in the speakup documentation. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
Reviewed-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
Thanks!
> ---
> Documentation/admin-guide/spkguide.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/spkguide.txt b/Documentation/admin-guide/spkguide.txt
> index 977ab3f5a0a8..1265c1eab31c 100644
> --- a/Documentation/admin-guide/spkguide.txt
> +++ b/Documentation/admin-guide/spkguide.txt
> @@ -543,7 +543,7 @@ As mentioned earlier, Speakup can either be completely compiled into the
> kernel, with the exception of the help module, or it can be compiled as
> a series of modules. When compiled as modules, Speakup will only be
> able to speak some of the bootup messages if your system administrator
> -has configured the system to load the modules at boo time. The modules
> +has configured the system to load the modules at boot time. The modules
> can be loaded after the file systems have been checked and mounted, or
> from an initrd. There is a third possibility. Speakup can be compiled
> with some components built into the kernel, and others as modules. As
> --
> 2.32.0
>
next prev parent reply other threads:[~2021-10-28 18:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 18:23 Colin Ian King
2021-10-28 18:24 ` Samuel Thibault [this message]
2021-11-01 17:19 ` Jonathan Corbet
2021-11-01 17:33 ` Samuel Thibault
2021-11-01 19:27 ` Joe Perches
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=20211028182451.baizgvczghh37zfl@begin \
--to=samuel.thibault@ens-lyon.org \
--cc=colin.i.king@googlemail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--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 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®