From: Artem Bityutskiy <dedekind1@gmail.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>,
Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
Ext4 Mailing List <linux-ext4@vger.kernel.org>,
Linux FS Maling List <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCHv3 0/4] ext4: stop using write_supers and s_dirt
Date: Tue, 03 Jul 2012 15:07:25 +0300 [thread overview]
Message-ID: <1341317245.2979.58.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1341316810-22598-1-git-send-email-dedekind1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
On Tue, 2012-07-03 at 15:00 +0300, Artem Bityutskiy wrote:
> Like the other similar patch-sets, we switch to a delayed job for writing out
> the superblock instead of using the 's_dirt' flag. Additionally, this patch-set
> includes several clean-ups.
Sorry, this paragraph is wrong, ignore it (copy-paste error). These
patches are the same as I sent at the beginning of April
(https://lkml.org/lkml/2012/4/2/111). Just refreshed and re-tested on
top of v3.5-rc5.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-07-03 12:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 12:00 [PATCHv3 0/4] ext4: stop using write_supers and s_dirt Artem Bityutskiy
2012-07-03 12:00 ` [PATCHv3 1/4] ext4: Remove useless marking of superblock dirty Artem Bityutskiy
2012-07-03 12:00 ` [PATCHv3 2/4] ext4: Convert last user of ext4_mark_super_dirty() to ext4_handle_dirty_super() Artem Bityutskiy
2012-07-03 12:00 ` [PATCHv3 3/4] ext4: remove unnecessary superblock dirtying Artem Bityutskiy
2012-07-03 12:48 ` Jan Kara
2012-07-04 12:25 ` Artem Bityutskiy
2012-07-03 12:00 ` [PATCHv3 4/4] ext4: weed out ext4_write_super Artem Bityutskiy
2012-07-03 12:07 ` Artem Bityutskiy [this message]
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=1341317245.2979.58.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).