public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Masanari Iida <standby24x7@gmail.com>
Cc: trivial@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [trivial] Fix typo in various Kconfig file
Date: Mon, 16 Apr 2012 12:32:45 -0700	[thread overview]
Message-ID: <4F8C73DD.3080804@xenotime.net> (raw)
In-Reply-To: <1334330051-20051-1-git-send-email-standby24x7@gmail.com>

On 04/13/2012 08:14 AM, Masanari Iida wrote:

> Correct spelling typo in various Kconfig file.
> 
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
>  arch/m68k/Kconfig.cpu                  |    2 +-
>  arch/mips/Kconfig                      |    4 ++--
>  arch/mips/Kconfig.debug                |    2 +-
>  arch/openrisc/Kconfig                  |    2 +-
>  arch/powerpc/platforms/Kconfig.cputype |    4 ++--
>  arch/powerpc/platforms/pseries/Kconfig |    2 +-
>  arch/sh/Kconfig.cpu                    |    2 +-
>  drivers/devfreq/Kconfig                |    2 +-
>  drivers/hid/Kconfig                    |    2 +-
>  drivers/hwmon/Kconfig                  |    2 +-
>  drivers/i2c/busses/Kconfig             |    2 +-
>  drivers/mfd/Kconfig                    |    6 +++---
>  drivers/ptp/Kconfig                    |    2 +-
>  drivers/watchdog/Kconfig               |    2 +-
>  drivers/xen/Kconfig                    |    2 +-
>  15 files changed, 19 insertions(+), 19 deletions(-)

Acked-by: Randy Dunlap <rdunlap@xenotime.net>

A few more possible corrections are noted below.

Thanks.


> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
> index ce30e2f..923a6c3 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/Kconfig
> @@ -1001,12 +1001,12 @@ config HOLES_IN_ZONE
>  	bool
>  
>  #
> -# Endianess selection.  Sufficiently obscure so many users don't know what to
> +# Endianness selection.  Sufficiently obscure so many users don't know what to
>  # answer,so we try hard to limit the available choices.  Also the use of a


space after ','

>  # choice statement should be more obvious to the user.
>  #
>  choice
> -	prompt "Endianess selection"
> +	prompt "Endianness selection"
>  	help
>  	  Some MIPS machines can be configured for either little or big endian
>  	  byte order. These modes require different kernels and a different
> diff --git a/arch/openrisc/Kconfig b/arch/openrisc/Kconfig
> index a478719..66dff20 100644
> --- a/arch/openrisc/Kconfig
> +++ b/arch/openrisc/Kconfig
> @@ -141,7 +141,7 @@ config DEBUG_STACKOVERFLOW
>  	bool "Check for kernel stack overflow"
>  	default y
>  	help
> -	  Make extra checks for space avaliable on stack in some
> +	  Make extra checks for space available on stack in some
>            critical functions. This will cause kernel to run a bit slower,
>  	  but will catch most of kernel stack overruns and exit gracefuly.


	                                                        gracefully.

>  


-- 
~Randy

      reply	other threads:[~2012-04-16 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 15:14 [PATCH] [trivial] Fix typo in various Kconfig file Masanari Iida
2012-04-16 19:32 ` Randy Dunlap [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=4F8C73DD.3080804@xenotime.net \
    --to=rdunlap@xenotime.net \
    --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