From: Jan Kara <jack@suse.cz>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Ext4 Mailing List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext2: do not register write_super within VFS
Date: Wed, 11 Apr 2012 17:30:54 +0200 [thread overview]
Message-ID: <20120411153054.GA16008@quack.suse.cz> (raw)
In-Reply-To: <1334143474.13842.0.camel@sauron.fi.intel.com>
On Wed 11-04-12 14:24:34, Artem Bityutskiy wrote:
> On Wed, 2012-04-04 at 00:36 +0200, Jan Kara wrote:
> > On Tue 03-04-12 12:49:18, Artem Bityutskiy wrote:
> > > From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> > >
> > > Jan Kara removed 'sb->s_dirt' VFS flag references, so we do not need to
> > > register the ext2 'ext2_write_super()' method in the VFS superblock operations,
> > > because 'sb->s_dirt' won't be ever set to 1 and VFS won't ever call
> > > '->write_super()' anyway. Thus, remove the method.
> > >
> > > Tested using xfstests.
> > >
> > > Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> > Thanks. Added to my tree.
>
> Jan, I do not see this patch in 'for_next' of your tree.
Yeah, it's not. So far it was in my for_next_testing and for_testing
branches. Once the branch (for_testing) passes some compile tests (done)
and runtime tests with xfstests I will update for_next branch to include
the patch as well. Because merge window is far, I don't hurry with that
very much. But if it causes problems for you I can run the tests and update
for_next tonight or tomorrow.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2012-04-11 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 9:49 [PATCH] ext2: do not register write_super within VFS Artem Bityutskiy
2012-04-03 22:36 ` Jan Kara
2012-04-11 11:24 ` Artem Bityutskiy
2012-04-11 15:30 ` Jan Kara [this message]
2012-04-11 15:40 ` 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=20120411153054.GA16008@quack.suse.cz \
--to=jack@suse.cz \
--cc=dedekind1@gmail.com \
--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