From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Colin King <colin.king@canonical.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
linux-usb@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] usb: xhci: fix spelling mistake in Kconfig "firwmare" -> "firmware"
Date: Thu, 18 Jun 2020 08:40:26 +0000 [thread overview]
Message-ID: <20200618084026.GA1073692@kroah.com> (raw)
In-Reply-To: <20200603121152.16550-1-colin.king@canonical.com>
On Wed, Jun 03, 2020 at 01:11:52PM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There are two spelling mistakes in the Kconfig text. Fix these.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/usb/host/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
> index 62c348062e48..5f4b6c71392c 100644
> --- a/drivers/usb/host/Kconfig
> +++ b/drivers/usb/host/Kconfig
> @@ -44,10 +44,10 @@ config USB_XHCI_PCI
> default y
>
> config USB_XHCI_PCI_RENESAS
> - tristate "Support for additional Renesas xHCI controller with firwmare"
> + tristate "Support for additional Renesas xHCI controller with firmware"
> ---help---
> Say 'Y' to enable the support for the Renesas xHCI controller with
> - firwmare. Make sure you have the firwmare for the device and
> + firmware. Make sure you have the firwmare for the device and
> installed on your system for this device to work.
> If unsure, say 'N'.
>
> --
> 2.25.1
>
Does not apply to my tree :(
prev parent reply other threads:[~2020-06-18 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 12:11 [PATCH][next] usb: xhci: fix spelling mistake in Kconfig "firwmare" -> "firmware" Colin King
2020-06-03 12:15 ` NAK: " Colin Ian King
2020-06-03 12:20 ` Colin Ian King
2020-06-18 8:40 ` Greg Kroah-Hartman [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=20200618084026.GA1073692@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).