public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Ali Gholami Rudi <ali@rudi.ir>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][TRIVIAL] ext2: fix a typo in ext2.h
Date: Tue, 31 Mar 2009 15:14:25 +0200	[thread overview]
Message-ID: <20090331131424.GG20127@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20090330121927.GA2237@lilem.mirepesht>

  JFYI: Bounced the email to trivial@kernel.org. Please also CC this alias
when submitting such trivial patches. Thanks.

									Honza

> 
> Signed-off-by: Ali Gholami Rudi <ali@rudi.ir>
> ---
>  fs/ext2/ext2.h |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/ext2/ext2.h b/fs/ext2/ext2.h
> index 3203042..6888b2d 100644
> --- a/fs/ext2/ext2.h
> +++ b/fs/ext2/ext2.h
> @@ -27,7 +27,7 @@ struct ext2_inode_info {
>  	/*
>  	 * i_block_group is the number of the block group which contains
>  	 * this file's inode.  Constant across the lifetime of the inode,
> -	 * it is ued for making block allocation decisions - we try to
> +	 * it is used for making block allocation decisions - we try to
>  	 * place a file's data blocks near its inode block, and new inodes
>  	 * near to their parent directory's inode.
>  	 */
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
-- 
Jan Kara <jack@suse.cz>
SuSE CR Labs

  reply	other threads:[~2009-03-31 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30 12:19 [PATCH][TRIVIAL] ext2: fix a typo in ext2.h Ali Gholami Rudi
2009-03-31 13:14 ` Jan Kara [this message]
2009-04-01  8:48 ` 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=20090331131424.GG20127@atrey.karlin.mff.cuni.cz \
    --to=jack@suse.cz \
    --cc=ali@rudi.ir \
    --cc=linux-ext4@vger.kernel.org \
    --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