Re: [PATCH 2/4] kconfig: trivial: fix typos

[Jean Delvare]

Hi Martin,

On Wed, 02 Oct 2013 07:24:27 +0200, Martin Walch wrote:
> From: Martin Walch <walch.martin@xxxxxx>
> Date: Wed, 2 Oct 2013 06:56:45 +0200
> Subject: [PATCH 2/4] kconfig: trivial: fix typos
> 
> inser() -> insert(), tell -> tells, peoperty -> property
> 
> Signed-off-by: Martin Walch <walch.martin@xxxxxx>
> ---
>  scripts/kconfig/mconf.c  | 2 +-
>  scripts/kconfig/menu.c   | 2 +-
>  scripts/kconfig/symbol.c | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/scripts/kconfig/mconf.c b/scripts/kconfig/mconf.c
> index 2c39631..39abdae 100644
> --- a/scripts/kconfig/mconf.c
> +++ b/scripts/kconfig/mconf.c
> @@ -263,7 +263,7 @@ search_help[] = N_(
>  	"    Press the key in the (#) prefix to jump directly to that\n"
>  	"    location. You will be returned to the current search results\n"
>  	"    after exiting this new menu.\n"
> -	"o The 'Selects:' line tell what symbol will be automatically\n"
> +	"o The 'Selects:' line tells what symbols will be automatically\n"
>  	"  selected if this symbol is selected (y or m)\n"
>  	"o The 'Selected by' line tell what symbol has selected this symbol\n"
>  	"\n"

There are 5 occurrences of this spelling mistake in the paragraph.
Please fix them all. And while you're here, you may find that "what
symbols needs" has a spelling mistake too.

> diff --git a/scripts/kconfig/menu.c b/scripts/kconfig/menu.c
> index c1d5320..b970101 100644
> --- a/scripts/kconfig/menu.c
> +++ b/scripts/kconfig/menu.c
> @@ -597,7 +597,7 @@ static void get_prompt_str(struct gstr *r, struct property *prop,
>  }
>  
>  /*
> - * get peoperty of type P_SYMBOL
> + * get property of type P_SYMBOL
>   */
>  static struct property *get_symbol_prop(struct symbol *sym)
>  {
> diff --git a/scripts/kconfig/symbol.c b/scripts/kconfig/symbol.c
> index c9a6775..7caabdb 100644
> --- a/scripts/kconfig/symbol.c
> +++ b/scripts/kconfig/symbol.c
> @@ -1047,7 +1047,7 @@ sym_re_search_free:
>   * When we check for recursive dependencies we use a stack to save
>   * current state so we can print out relevant info to user.
>   * The entries are located on the call stack so no need to free memory.
> - * Note inser() remove() must always match to properly clear the stack.
> + * Note insert() remove() must always match to properly clear the stack.
>   */
>  static struct dep_stack {
>  	struct dep_stack *prev, *next;

Thanks,
-- 
Jean Delvare
Suse L3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/