All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
	viro@zeniv.linux.org.uk, jeffm@suse.com, chris.mason@oracle.com,
	reiserfs-devel@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] ext3: make ext3 mount default to barrier=1
Date: Mon, 11 Jul 2011 15:20:09 -0400	[thread overview]
Message-ID: <20110711192009.GA20887@infradead.org> (raw)
In-Reply-To: <20110711191735.GG5482@quack.suse.cz>

On Mon, Jul 11, 2011 at 09:17:35PM +0200, Jan Kara wrote:
> On Mon 11-07-11 14:25:59, Christoph Hellwig wrote:
> > From: Chris Mason <mason@suse.com>
> > 
> > This patch turns on barriers by default for ext3.  mount -o barrier=0
> > will turn them off.
> > 
> > Acked-by: Jeff Mahoney <jeffm@suse.com>
>   This patch misses signed-off-by. Feel free to add
> Acked-by: Jan Kara <jack@suse.cz>

I took it from the SuSE tree where it didn't have one either.  I hope
Jeff can add one, but if not I think it's trivial enough to bother.


  reply	other threads:[~2011-07-11 19:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 18:25 [PATCH 0/2] always default to issue cache flushes Christoph Hellwig
2011-07-11 18:25 ` [PATCH 1/2] ext3: make ext3 mount default to barrier=1 Christoph Hellwig
2011-07-11 19:17   ` Jan Kara
2011-07-11 19:20     ` Christoph Hellwig [this message]
2011-07-11 22:23     ` Ted Ts'o
2011-07-12  0:16   ` Eric Sandeen
2011-07-12 13:24   ` Chris Mason
2011-07-14 15:19     ` Christoph Hellwig
2011-07-11 18:26 ` [PATCH 2/2] reiserfs: make reiserfs default to barrier=flush Christoph Hellwig
2011-07-11 19:19 ` [PATCH 0/2] always default to issue cache flushes Jan Kara

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=20110711192009.GA20887@infradead.org \
    --to=hch@infradead.org \
    --cc=chris.mason@oracle.com \
    --cc=jack@suse.cz \
    --cc=jeffm@suse.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.