From: Ryusuke Konishi <ryusuke@osrg.net>
To: fweisbec@gmail.com
Cc: arnd@arndb.de, konishi.ryusuke@lab.ntt.co.jp,
linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, jblunck@suse.de
Subject: Re: [PATCH] nilfs2: remove BKL uses
Date: Tue, 06 Jul 2010 02:55:11 +0900 (JST) [thread overview]
Message-ID: <20100706.025511.266421917.ryusuke@osrg.net> (raw)
In-Reply-To: <20100705145324.GA5240@nowhere>
On Mon, 5 Jul 2010 16:53:29 +0200, Frederic Weisbecker wrote:
> On Mon, Jul 05, 2010 at 04:50:23PM +0200, Arnd Bergmann wrote:
> > On Sunday 04 July 2010, Ryusuke Konishi wrote:
> > > Nilfs has BKL uses in its put_super and remount functions, but none of
> > > them are necessary, just came from earlier push downs. This
> > > eliminates the BKL uses from nilfs.
> > >
> > > Signed-off-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
> >
> > This looks good, but there is a another patch series pushing the BKL
> > into the get_sb and fill_super operations, which should be the final
> > pushdown for file systems. I wonder if there is a way to find a
> > shortcut on this so we don't need to add it first just to have you
> > go through the effort of removing it again.
>
>
> I could take his patch in the mount pushdown series.
OK, please treat this patch as needed.
I've forgotten the additional BKL push down patch and Jan's BKL
removal patch on nilfs, but yes, it looks omissible to add BKL and
remove it again there.
For now, I will drop my patch from my tree.
Thanks,
Ryusuke Konishi
prev parent reply other threads:[~2010-07-05 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-04 5:22 [PATCH] nilfs2: remove BKL uses Ryusuke Konishi
[not found] ` <1278220928-28121-1-git-send-email-konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2010-07-05 14:50 ` Arnd Bergmann
[not found] ` <201007051650.23761.arnd-r2nGTMty4D4@public.gmane.org>
2010-07-05 14:53 ` Frederic Weisbecker
2010-07-05 17:55 ` Ryusuke Konishi [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=20100706.025511.266421917.ryusuke@osrg.net \
--to=ryusuke@osrg.net \
--cc=arnd@arndb.de \
--cc=fweisbec@gmail.com \
--cc=jblunck@suse.de \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@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