From: Randy Dunlap <rdunlap@infradead.org>
To: Masanari Iida <standby24x7@gmail.com>,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH][trivial] Kconfig: Fix typos in Kconfig
Date: Mon, 25 Sep 2017 08:39:55 -0700 [thread overview]
Message-ID: <458204cb-3901-4c3d-82c8-d8735d91a1b2@infradead.org> (raw)
In-Reply-To: <20170925045530.25333-1-standby24x7@gmail.com>
On 09/24/17 21:55, Masanari Iida wrote:
> This patch fix some spelling typos found in Kconfig files.
>
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> diff --git a/arch/arm/mach-bcm/Kconfig b/arch/arm/mach-bcm/Kconfig
> index 73be3d578851..0bb7e74e1d87 100644
> --- a/arch/arm/mach-bcm/Kconfig
> +++ b/arch/arm/mach-bcm/Kconfig
> @@ -69,7 +69,7 @@ config ARCH_BCM_5301X
>
> This is a network SoC line mostly used in home routers and
> wifi access points, it's internal name is Northstar.
its
> - This inclused the following SoC: BCM53010, BCM53011, BCM53012,
> + This include the following SoC: BCM53010, BCM53011, BCM53012,
includes
> BCM53014, BCM53015, BCM53016, BCM53017, BCM53018, BCM4707,
> BCM4708 and BCM4709.
>
> diff --git a/arch/xtensa/Kconfig b/arch/xtensa/Kconfig
> index 7ad6d77b2f22..9b8747ed3134 100644
> --- a/arch/xtensa/Kconfig
> +++ b/arch/xtensa/Kconfig
> @@ -223,7 +223,7 @@ config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
> then enter your normal kernel breakpoints once the MMU was mapped
> to the kernel mappings (0XC0000000).
>
> - This unfortunately doesn't work for U-Boot and likley also wont
> + This unfortunately doesn't work for U-Boot and likely also wont
won't
> work for using KEXEC to have a hot kernel ready for doing a
> KDUMP.
>
Thanks.
--
~Randy
next prev parent reply other threads:[~2017-09-25 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 4:55 Masanari Iida
2017-09-25 15:39 ` Randy Dunlap [this message]
2017-09-26 3:47 ` [PATCH/v2] " Masanari Iida
2017-09-26 15:22 ` Randy Dunlap
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=458204cb-3901-4c3d-82c8-d8735d91a1b2@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=standby24x7@gmail.com \
--cc=trivial@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®