mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Masanari Iida <standby24x7@gmail.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] [trivial] Fix typo in various Kconfig
Date: Tue, 07 Aug 2012 09:46:33 -0700	[thread overview]
Message-ID: <50214669.2020200@xenotime.net> (raw)
In-Reply-To: <1344347699-26434-1-git-send-email-standby24x7@gmail.com>

On 08/07/2012 06:54 AM, Masanari Iida wrote:

> Correct spelling typo in various Kconfig files.
> 
> Signed-off-by: Masanari Iida <standby24x7@gmail.com>
> ---
>  arch/arm/mach-omap2/Kconfig      |  2 +-
>  arch/arm/mach-tegra/Kconfig      |  2 +-
>  arch/blackfin/mach-bf609/Kconfig |  2 +-
>  arch/openrisc/Kconfig            |  2 +-
>  crypto/Kconfig                   |  2 +-
>  drivers/hwspinlock/Kconfig       |  2 +-
>  drivers/md/Kconfig               |  2 +-
>  drivers/media/video/Kconfig      |  2 +-
>  drivers/thermal/Kconfig          |  2 +-
>  drivers/tty/serial/8250/Kconfig  |  2 +-
>  drivers/usb/host/Kconfig         |  4 ++--
>  lib/Kconfig.debug                | 10 +++++-----
>  12 files changed, 17 insertions(+), 17 deletions(-)
> 



We normally accept either British or American spellings,
so these don't need to be changed.  The rest are OK.

Thanks.

> diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
> index dd2db02..60b026a 100644
> --- a/arch/arm/mach-omap2/Kconfig
> +++ b/arch/arm/mach-omap2/Kconfig
> @@ -399,7 +399,7 @@ config OMAP4_ERRATA_I688
>  	  before issuing WFI. This condition will be met if one Strongly ordered
>  	  access is performed to the target right before executing the WFI.
>  	  In MPU case, L3 T2ASYNC FIFO and DDR T2ASYNC FIFO needs to be drained.
> -	  IO barrier ensure that there is no synchronisation loss on initiators
> +	  IO barrier ensure that there is no synchronization loss on initiators
>  	  operating on both interconnect port simultaneously.
>  endmenu
>  
> diff --git a/drivers/hwspinlock/Kconfig b/drivers/hwspinlock/Kconfig
> index c7c3128..8ae898b 100644
> --- a/drivers/hwspinlock/Kconfig
> +++ b/drivers/hwspinlock/Kconfig
> @@ -24,7 +24,7 @@ config HSEM_U8500
>  	select HWSPINLOCK
>  	help
>  	  Say y here to support the STE Hardware Semaphore functionality, which
> -	  provides a synchronisation mechanism for the various processor on the
> +	  provides a synchronization mechanism for the various processor on the
>  	  SoC.
>  
>  	  If unsure, say N.
> diff --git a/drivers/md/Kconfig b/drivers/md/Kconfig
> index d949b78..97f3f0b 100644
> --- a/drivers/md/Kconfig
> +++ b/drivers/md/Kconfig
> @@ -40,7 +40,7 @@ config MD_AUTODETECT
>  
>  	  If you don't use raid and say Y, this autodetection can cause 
>  	  a several-second delay in the boot time due to various
> -	  synchronisation steps that are part of this step.
> +	  synchronization steps that are part of this step.
>  
>  	  If unsure, say Y.
>  



-- 
~Randy

  reply	other threads:[~2012-08-07 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07 13:54 Masanari Iida
2012-08-07 16:46 ` Randy Dunlap [this message]
2012-08-07 17:17   ` Masanari Iida
2012-08-07 17:15 ` [PATCH/v2] " Masanari Iida
2012-08-07 17:34   ` 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=50214669.2020200@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

all inboxes | Powered by JetHome®