From: Arnd Bergmann <arnd@arndb.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: manual merge of the bkl-trivial tree with the hfsplus tree
Date: Mon, 4 Oct 2010 10:23:45 +0200 [thread overview]
Message-ID: <201010041023.45694.arnd@arndb.de> (raw)
In-Reply-To: <20101004033441.GA6867@lst.de>
On Monday 04 October 2010 05:34:41 Christoph Hellwig wrote:
> On Mon, Oct 04, 2010 at 10:47:40AM +1100, Stephen Rothwell wrote:
> > Hi Arnd,
> >
> > The second of the hfsplus tree commits seems to supercede the bkl-trivial
> > one, so I used that.
>
> Yes, the hfsplus tree contains a proper BKL removal for hfsplus.
Ok. I've removed the pushdown into hfsplus and subsequent removal from my
tree now, thanks! I've also removed the pushdown from other file systems
that are already BKL-free.
Christoph, are you planning to take care of freevxfs, too? I can't figure
out whether readdir and lookup actually need locking there.
Arnd
next prev parent reply other threads:[~2010-10-04 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 23:47 linux-next: manual merge of the bkl-trivial tree with the hfsplus tree Stephen Rothwell
2010-10-04 3:34 ` Christoph Hellwig
2010-10-04 8:23 ` Arnd Bergmann [this message]
2010-10-04 8:29 ` Christoph Hellwig
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=201010041023.45694.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).