From: Boaz Harrosh <bharrosh@panasas.com>
To: <dedekind1@gmail.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
Benny Halevy <bhalevy@tonian.com>, <osd-dev@open-osd.org>
Subject: Re: [PATCH] exofs: stop using s_dirt
Date: Wed, 27 Jun 2012 18:49:33 +0300 [thread overview]
Message-ID: <4FEB2B8D.7070909@panasas.com> (raw)
In-Reply-To: <1340281745.13910.211.camel@sauron.fi.intel.com>
On 06/21/2012 03:29 PM, Artem Bityutskiy wrote:
> On Mon, 2012-06-04 at 14:48 +0300, Artem Bityutskiy wrote:
>> From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
>>
>> Exofs has the '->write_super()' handler and makes some use of the '->s_dirt'
>> superblock flag, but it really needs neither of them because it never sets
>> 's_dirt' to one which means the VFS never calls its '->write_super()' handler.
>> Thus, remove both.
>>
>> Note, I am trying to remove both 's_dirt' and 'write_super()' from VFS
>> altogether once all users are gone.
>>
>> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
>
> Al or Boaz, would you please consider picking this patch?
>
I will
Sorry for the delay was sick and am only now coming back on.
It should all be included for the next merge window.
Thanks for doing this.
Boaz
prev parent reply other threads:[~2012-06-27 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 11:48 [PATCH] exofs: stop using s_dirt Artem Bityutskiy
2012-06-04 16:12 ` Boaz Harrosh
2012-06-05 7:35 ` Artem Bityutskiy
2012-06-05 10:35 ` Artem Bityutskiy
2012-06-05 13:02 ` Boaz Harrosh
2012-06-21 12:29 ` Artem Bityutskiy
2012-06-27 15:49 ` Boaz Harrosh [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=4FEB2B8D.7070909@panasas.com \
--to=bharrosh@panasas.com \
--cc=bhalevy@tonian.com \
--cc=dedekind1@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--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).