linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: David Brownell <dbrownell@users.sourceforge.net>,
	spi-devel-general@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] trivial: fix double "of of" in comment in spidev code
Date: Fri, 23 Oct 2009 03:48:31 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.00.0910230348210.8582@wotan.suse.de> (raw)
In-Reply-To: <1256240069-25223-1-git-send-email-cascardo@holoscopio.com>

On Thu, 22 Oct 2009, Thadeu Lima de Souza Cascardo wrote:

> Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
> ---
>  drivers/spi/spidev.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/spi/spidev.c b/drivers/spi/spidev.c
> index 5d23983..d9b4100 100644
> --- a/drivers/spi/spidev.c
> +++ b/drivers/spi/spidev.c
> @@ -42,7 +42,7 @@
>   * This supports acccess to SPI devices using normal userspace I/O calls.
>   * Note that while traditional UNIX/POSIX I/O semantics are half duplex,
>   * and often mask message boundaries, full SPI support requires full duplex
> - * transfers.  There are several kinds of of internal message boundaries to
> + * transfers.  There are several kinds of internal message boundaries to
>   * handle chipselect management and other protocol options.

Applied, thanks.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

      reply	other threads:[~2009-10-23  1:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22 19:34 [PATCH 1/2] trivial: fix double "of of" in comment in spidev code Thadeu Lima de Souza Cascardo
2009-10-23  1:48 ` Jiri Kosina [this message]

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=alpine.LSU.2.00.0910230348210.8582@wotan.suse.de \
    --to=jkosina@suse.cz \
    --cc=cascardo@holoscopio.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spi-devel-general@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).