From: Theodore Ts'o <tytso@mit.edu>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 1/6] jbd2: optimize jbd2_journal_force_commit
Date: Mon, 10 Jun 2013 09:53:57 -0400 [thread overview]
Message-ID: <20130610135357.GC23051@thunk.org> (raw)
In-Reply-To: <87ehcaw1d0.fsf@openvz.org>
On Mon, Jun 10, 2013 at 05:18:19PM +0400, Dmitry Monakhov wrote:
> > Have you had a chance to work on an updated version of this series
> > with Jan's requested changes?
> Yes. It is ready, but since Jan is on vacations till 20'th I thought
> it is useless to send it before that date. Am I right?
Please send it now; other folks, including myself, can review it.
Since we are already at 3.10-rc5, I'd get the ext4/jbd2-related
patches reviewed and in the ext4 tree sooner rather than later.
Many thanks!!
- Ted
next prev parent reply other threads:[~2013-06-10 13:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 9:18 [PATCH 0/6] ext3/4 data integrity fixes Dmitry Monakhov
2013-05-28 9:18 ` [PATCH 1/6] jbd2: optimize jbd2_journal_force_commit Dmitry Monakhov
2013-05-28 21:22 ` Jan Kara
2013-06-03 11:16 ` Dmitry Monakhov
2013-06-10 13:07 ` Theodore Ts'o
2013-06-10 13:18 ` Dmitry Monakhov
2013-06-10 13:53 ` Theodore Ts'o [this message]
2013-05-28 9:18 ` [PATCH 2/6] ext4: fix data integrity for ext4_sync_fs Dmitry Monakhov
2013-05-28 21:51 ` Jan Kara
2013-06-03 11:30 ` Dmitry Monakhov
2013-05-28 9:18 ` [PATCH 3/6] jbd: optimize journal_force_commit Dmitry Monakhov
2013-05-28 9:18 ` [PATCH 4/6] ext3: fix data integrity for ext4_sync_fs Dmitry Monakhov
2013-05-28 21:40 ` Jan Kara
2013-05-28 9:19 ` [PATCH 5/6] ext4: Fix fsync error handling after filesystem abort Dmitry Monakhov
2013-05-28 21:29 ` Jan Kara
2013-05-28 9:19 ` [PATCH 6/6] ext3: " Dmitry Monakhov
2013-05-28 21:33 ` 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=20130610135357.GC23051@thunk.org \
--to=tytso@mit.edu \
--cc=dmonakhov@openvz.org \
--cc=jack@suse.cz \
--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).