linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: linux-ext4@vger.kernel.org
Subject: [PATCH][TRIVIAL] Documentation/filesystems/ext4.txt  barriers -> barrier
Date: Thu, 21 Mar 2013 16:31:21 +0100	[thread overview]
Message-ID: <20130321153121.GA17388@panda> (raw)

[-- Attachment #1: Type: text/plain, Size: 84 bytes --]

Hello list,

I've found a small typo in Documentation/filesystems/ext4.txt

	Sander

[-- Attachment #2: ext4-doc.patch --]
[-- Type: text/x-diff, Size: 893 bytes --]

diff -ruN linux-3.9-rc3-orig/Documentation/filesystems/ext4.txt linux-3.9-rc3/Documentation/filesystems/ext4.txt
--- linux-3.9-rc3-orig/Documentation/filesystems/ext4.txt	2013-03-17 23:59:32.000000000 +0100
+++ linux-3.9-rc3/Documentation/filesystems/ext4.txt	2013-03-21 18:27:19.246017488 +0100
@@ -65,7 +65,7 @@
     note that ext4 enables write barriers by default, while ext3 does
     not enable write barriers by default.  So it is useful to use
     explicitly specify whether barriers are enabled or not when via the
-    '-o barriers=[0|1]' mount option for both ext3 and ext4 filesystems
+    '-o barrier=[0|1]' mount option for both ext3 and ext4 filesystems
     for a fair comparison.  When tuning ext3 for best benchmark numbers,
     it is often worthwhile to try changing the data journaling mode; '-o
     data=writeback' can be faster for some workloads.  (Note however that

             reply	other threads:[~2013-03-21 15:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 15:31 Sander [this message]
2013-04-06 20:49 ` [TRIVIAL] Documentation/filesystems/ext4.txt barriers -> barrier 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=20130321153121.GA17388@panda \
    --to=sander@humilis.net \
    --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).