linux-kernel - Re: [PATCH] treewide: Fix typo in Documentation/DocBook/device-drivers

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20141022114917.3b34905d@lwn.net>
Date:	Wed, 22 Oct 2014 11:49:17 -0400
From:	Jonathan Corbet <corbet@....net>
To:	Masanari Iida <standby24x7@...il.com>
Cc:	trivial@...nel.org, rdunlap@...radead.org,
	linux-kernel@...r.kernel.org,
	Sumit Semwal <sumit.semwal@...aro.org>,
	Wolfram Sang <wsa@...-dreams.de>
Subject: Re: [PATCH] treewide: Fix typo in
 Documentation/DocBook/device-drivers

On Wed, 22 Oct 2014 00:00:14 +0900
Masanari Iida <standby24x7@...il.com> wrote:

> This patch fix speeling typo found in html files within
> Documentation/DocBook/device-drivers.
> It is because html files are generated from comments in source,
> so I have to fix comments in the source.
> 
> Signed-off-by: Masanari Iida <standby24x7@...il.com>

I can pick this up, I guess.  But I'll copy the relevant subsystem
maintainers just in case they would rather carry the changes themselves.

jon

> ---
>  drivers/dma-buf/fence.c | 2 +-
>  include/linux/fence.h   | 4 ++--
>  include/linux/i2c.h     | 2 +-
>  3 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/dma-buf/fence.c b/drivers/dma-buf/fence.c
> index 7bb9d65..e554111 100644
> --- a/drivers/dma-buf/fence.c
> +++ b/drivers/dma-buf/fence.c
> @@ -283,7 +283,7 @@ EXPORT_SYMBOL(fence_add_callback);
>   * @cb:		[in]	the callback to remove
>   *
>   * Remove a previously queued callback from the fence. This function returns
> - * true if the callback is succesfully removed, or false if the fence has
> + * true if the callback is successfully removed, or false if the fence has
>   * already been signaled.
>   *
>   * *WARNING*:
> diff --git a/include/linux/fence.h b/include/linux/fence.h
> index d174585..39efee1 100644
> --- a/include/linux/fence.h
> +++ b/include/linux/fence.h
> @@ -128,8 +128,8 @@ struct fence_cb {
>   * from irq context, so normal spinlocks can be used.
>   *
>   * A return value of false indicates the fence already passed,
> - * or some failure occured that made it impossible to enable
> - * signaling. True indicates succesful enabling.
> + * or some failure occurred that made it impossible to enable
> + * signaling. True indicates successful enabling.
>   *
>   * fence->status may be set in enable_signaling, but only when false is
>   * returned.
> diff --git a/include/linux/i2c.h b/include/linux/i2c.h
> index b556e0a..70ee0d3 100644
> --- a/include/linux/i2c.h
> +++ b/include/linux/i2c.h
> @@ -359,7 +359,7 @@ i2c_register_board_info(int busnum, struct i2c_board_info const *info,
>   * to name two of the most common.
>   *
>   * The return codes from the @master_xfer field should indicate the type of
> - * error code that occured during the transfer, as documented in the kernel
> + * error code that occurred during the transfer, as documented in the kernel
>   * Documentation file Documentation/i2c/fault-codes.
>   */
>  struct i2c_algorithm {
--
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/