linux-kernel - Re: [PATCH][TRIVIAL] uwb: Fix misspelling of neighbourhood in comment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 21 Jul 2011 14:03:56 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Jesper Juhl <jj@...osbits.net>
Cc:	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
	Inaky Perez-Gonzalez <inaky.perez-gonzalez@...el.com>
Subject: Re: [PATCH][TRIVIAL] uwb: Fix misspelling of neighbourhood in
 comment

On Sun, 17 Jul 2011, Jesper Juhl wrote:

> In drivers/uwb/uwbd.c, the word 'neighbourhood' is misspelled as
> 'neighboorhood' in a comment. Fix that.
> 
> Signed-off-by: Jesper Juhl <jj@...osbits.net>
> ---
>  drivers/uwb/uwbd.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/uwb/uwbd.c b/drivers/uwb/uwbd.c
> index 001c8b4..bdcb13c 100644
> --- a/drivers/uwb/uwbd.c
> +++ b/drivers/uwb/uwbd.c
> @@ -256,7 +256,7 @@ static void uwbd_event_handle(struct uwb_event *evt)
>   * UWB Daemon
>   *
>   * Listens to all UWB notifications and takes care to track the state
> - * of the UWB neighboorhood for the kernel. When we do a run, we
> + * of the UWB neighbourhood for the kernel. When we do a run, we
>   * spinlock, move the list to a private copy and release the
>   * lock. Hold it as little as possible. Not a conflict: it is
>   * guaranteed we own the events in the private list.

Applied.

-- 
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/