mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <jj@chaosbits.net>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Jiri Kosina <trivial@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [TRIVIAL] fix comment typo initilaization
Date: Tue, 15 Feb 2011 00:10:27 +0100 (CET)	[thread overview]
Message-ID: <alpine.LNX.2.00.1102150009050.4530@swampdragon.chaosbits.net> (raw)
In-Reply-To: <1297724802.1793.36.camel@t41.thuisdomein>

On Tue, 15 Feb 2011, Paul Bolle wrote:

> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
>  fs/fuse/cuse.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/fuse/cuse.c b/fs/fuse/cuse.c
> index 3e87cce..7c39b88 100644
> --- a/fs/fuse/cuse.c
> +++ b/fs/fuse/cuse.c
> @@ -458,7 +458,7 @@ static void cuse_fc_release(struct fuse_conn *fc)
>   * @file: file struct being opened
>   *
>   * Userland CUSE server can create a CUSE device by opening /dev/cuse
> - * and replying to the initilaization request kernel sends.  This
> + * and replying to the initialization request kernel sends.  This
>   * function is responsible for handling CUSE device initialization.
>   * Because the fd opened by this function is used during
>   * initialization, this function only creates cuse_conn and sends
> 

Trivial and obviously correct. But since I actually took the time to 
verify the spelling, I'll add my reviewed-by ;-)

Reviewed-by: Jesper Juhl <jj@chaosbits.net>


-- 
Jesper Juhl <jj@chaosbits.net>            http://www.chaosbits.net/
Plain text mails only, please.
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html


  reply	other threads:[~2011-02-14 23:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 23:05 Paul Bolle
2011-02-14 23:10 ` Jesper Juhl [this message]
2011-02-15  9:26 ` Jiri Kosina

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.LNX.2.00.1102150009050.4530@swampdragon.chaosbits.net \
    --to=jj@chaosbits.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=trivial@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

all inboxes | Powered by JetHome®