From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ted Ts'o <tytso@mit.edu>
Cc: Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
Ext4 Mailing List <linux-ext4@vger.kernel.org>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v2 1/4] ext4: Remove useless marking of superblock dirty
Date: Thu, 21 Jun 2012 16:11:45 +0300 [thread overview]
Message-ID: <1340284305.13910.216.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20120601151601.GA13826@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 328 bytes --]
On Fri, 2012-06-01 at 11:16 -0400, Ted Ts'o wrote:
> I will make sure this patchset
> gets reviewed and queued for 3.5.
Hi Ted,
just a reminder. The patch does not apply cleanly but the conflicts are
simple and they are around the SB checksum stuff. Do you want me to
re-send?
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-21 13:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 11:45 [PATCH v2 0/4] do not use s_dirt in ext4 Artem Bityutskiy
2012-04-02 11:45 ` [PATCH v2 1/4] ext4: Remove useless marking of superblock dirty Artem Bityutskiy
2012-04-12 7:20 ` Artem Bityutskiy
2012-04-30 8:37 ` Artem Bityutskiy
2012-06-01 13:53 ` Artem Bityutskiy
2012-06-01 13:55 ` Artem Bityutskiy
2012-06-01 15:16 ` Ted Ts'o
2012-06-01 17:48 ` Artem Bityutskiy
2012-06-21 13:11 ` Artem Bityutskiy [this message]
2012-04-02 11:45 ` [PATCH v2 2/4] ext4: Convert last user of ext4_mark_super_dirty() to ext4_handle_dirty_super() Artem Bityutskiy
2012-04-02 11:45 ` Artem Bityutskiy
2012-04-02 11:45 ` [PATCH v2 3/4] ext4: remove unnecessary superblock dirtying Artem Bityutskiy
2012-04-02 21:49 ` Jan Kara
2012-04-02 11:45 ` [PATCH v2 4/4] ext4: weed out ext4_write_super Artem Bityutskiy
2012-04-02 21:50 ` Jan Kara
2012-05-18 10:25 ` [PATCH v2 0/4] do not use s_dirt in ext4 Artem Bityutskiy
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=1340284305.13910.216.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).