linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jon ERNST" <jonernst@gmx.com>
To: linux-ext4@vger.kernel.org
Subject: extents_status comment small modification
Date: Thu, 31 Jan 2013 07:08:34 +0100	[thread overview]
Message-ID: <20130131060835.23270@gmx.com> (raw)

 Hi list,
 
 I guess is a small helpful typo fix.
 
 diff --git a/fs/ext4/extents_status.c b/fs/ext4/extents_status.c
 index 564d981..ca4c810 100644
 --- a/fs/ext4/extents_status.c
 +++ b/fs/ext4/extents_status.c
 @@ -104,7 +104,7 @@
   *     a space.
   *
   *   --        race on a delayed extent tree
 - *     Delayed extent tree is protected inode->i_es_lock.
 + *     Delayed extent tree is protected by inode->i_es_lock.
   *
   *
   * ==========================================================================
 
 
 Regards,
 Jon
--
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

             reply	other threads:[~2013-01-31  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31  6:08 Jon ERNST [this message]
2013-02-01  4:19 ` extents_status comment small modification Theodore Ts'o

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=20130131060835.23270@gmx.com \
    --to=jonernst@gmx.com \
    --cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).