mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Masanari Iida <standby24x7@gmail.com>
Cc: trivial@kernel.org, rdunlap@infradead.org,
	linux-kernel@vger.kernel.org,
	Sumit Semwal <sumit.semwal@linaro.org>,
	Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH] treewide: Fix typo in Documentation/DocBook/device-drivers
Date: Wed, 22 Oct 2014 11:49:17 -0400	[thread overview]
Message-ID: <20141022114917.3b34905d@lwn.net> (raw)
In-Reply-To: <1413903614-20775-1-git-send-email-standby24x7@gmail.com>

On Wed, 22 Oct 2014 00:00:14 +0900
Masanari Iida <standby24x7@gmail.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@gmail.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 {

  parent reply	other threads:[~2014-10-22 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 15:00 Masanari Iida
2014-10-21 22:12 ` Randy Dunlap
2014-10-22 15:49 ` Jonathan Corbet [this message]
2014-10-22 15:55   ` Wolfram Sang

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=20141022114917.3b34905d@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=standby24x7@gmail.com \
    --cc=sumit.semwal@linaro.org \
    --cc=trivial@kernel.org \
    --cc=wsa@the-dreams.de \
    /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

Powered by JetHome