From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Jens Axboe <axboe@kernel.dk>, Theodore Tso <tytso@mit.edu>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Jeff Layton <jlayton@redhat.com>,
Dave Chinner <david@fromorbit.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org, Chris Mason <chris.mason@oracle.com>,
Joel Becker <jlbec@evilplan.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org, Mingming Cao <mcao@us.ibm.com>
Subject: Re: [PATCHSET v3.2 0/3] data integrity: Stabilize pages during writeback for various fses
Date: Fri, 27 May 2011 03:33:26 -0400 [thread overview]
Message-ID: <20110527073326.GA15405@infradead.org> (raw)
In-Reply-To: <20110519224841.28755.80650.stgit@elm3c44.beaverton.ibm.com>
Can you resend patches 1 and 2 ontop of current Linus' tree with Jans
page_mkwrite changes? I don't think there's much point of patch 3 until
we get a user for simple_page_mkwrite.
next prev parent reply other threads:[~2011-05-27 7:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 22:48 [PATCHSET v3.2 0/3] data integrity: Stabilize pages during writeback for various fses Darrick J. Wong
2011-05-19 22:48 ` [PATCH 1/3] mm: Wait for writeback when grabbing pages to begin a write Darrick J. Wong
2011-05-19 22:48 ` [PATCH 2/3] fs: block_page_mkwrite should wait for writeback to finish Darrick J. Wong
2011-05-19 22:49 ` [PATCH 3/3] mm: Provide stub page_mkwrite functionality to stabilize pages during writes Darrick J. Wong
2011-05-27 7:33 ` Christoph Hellwig [this message]
2011-05-27 16:20 ` [PATCHSET v3.2 0/3] data integrity: Stabilize pages during writeback for various fses Darrick J. Wong
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=20110527073326.GA15405@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=chris.mason@oracle.com \
--cc=dave@linux.vnet.ibm.com \
--cc=david@fromorbit.com \
--cc=djwong@us.ibm.com \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=jlbec@evilplan.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mcao@us.ibm.com \
--cc=tytso@mit.edu \
--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 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).