public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	i2c@lm-sensors.org
Subject: Re: [PATCH] drivers/i2c/: Spelling fixes
Date: Mon, 17 Dec 2007 21:32:22 +0100	[thread overview]
Message-ID: <20071217213222.09350886@hyperion.delvare> (raw)
In-Reply-To: <1197919875-5288-35-git-send-email-joe@perches.com>

Hi Joe,

On Mon, 17 Dec 2007 11:30:34 -0800, Joe Perches wrote:
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>  drivers/i2c/busses/i2c-at91.c     |    2 +-
>  drivers/i2c/busses/i2c-powermac.c |    2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/i2c/busses/i2c-at91.c b/drivers/i2c/busses/i2c-at91.c
> index 9c8b6d5..c09b036 100644
> --- a/drivers/i2c/busses/i2c-at91.c
> +++ b/drivers/i2c/busses/i2c-at91.c
> @@ -135,7 +135,7 @@ static int xfer_write(struct i2c_adapter *adap, unsigned char *buf, int length)
>   * Generic i2c master transfer entrypoint.
>   *
>   * Note: We do not use Atmel's feature of storing the "internal device address".
> - * Instead the "internal device address" has to be written using a seperate
> + * Instead the "internal device address" has to be written using a separate
>   * i2c message.
>   * http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2004-September/024411.html
>   */
> diff --git a/drivers/i2c/busses/i2c-powermac.c b/drivers/i2c/busses/i2c-powermac.c
> index 0ab4f26..7813127 100644
> --- a/drivers/i2c/busses/i2c-powermac.c
> +++ b/drivers/i2c/busses/i2c-powermac.c
> @@ -94,7 +94,7 @@ static s32 i2c_powermac_smbus_xfer(	struct i2c_adapter*	adap,
>  	    	break;
>  
>  	/* Note that these are broken vs. the expected smbus API where
> -	 * on reads, the lenght is actually returned from the function,
> +	 * on reads, the length is actually returned from the function,
>  	 * but I think the current API makes no sense and I don't want
>  	 * any driver that I haven't verified for correctness to go
>  	 * anywhere near a pmac i2c bus anyway ...

Applied, thank you.

-- 
Jean Delvare

  reply	other threads:[~2007-12-17 20:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5703e57f925f31fc0eb38873bd7f10fc44f99cb4.1197918891.git.joe@perches.com>
2007-12-17 19:30 ` [PATCH] drivers/edac/: Spelling fixes Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/firmware/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/i2c/: " Joe Perches
2007-12-17 20:32   ` Jean Delvare [this message]
2007-12-17 19:30 ` [PATCH] drivers/ide/: " Joe Perches
2007-12-17 20:53   ` Bartlomiej Zolnierkiewicz
2007-12-17 19:30 ` [PATCH] drivers/infiniband/: " Joe Perches
2007-12-18  5:48   ` Roland Dreier
2007-12-17 19:30 ` [PATCH] drivers/input/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/isdn/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/macintosh/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/media/: " Joe Perches
2007-12-17 19:30 ` [PATCH] include/media/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/message/: " Joe Perches
2007-12-17 19:30 ` [PATCH] drivers/mtd/: " Joe Perches
2007-12-17 19:36 ` Joe Perches
2007-12-17 19:40 ` Joe Perches
2007-12-17 20:40 ` [PATCH] drivers/net/: " Pavel Roskin
2007-12-17 20:47   ` Joe Perches

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=20071217213222.09350886@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=akpm@linux-foundation.org \
    --cc=i2c@lm-sensors.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.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