From: Arnd Bergmann <arnd@arndb.de>
To: Sage Weil <sage@newdream.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@linux.intel.com>,
Christoph Hellwig <hch@lst.de>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
"J. Bruce Fields" <bfields@fieldses.org>,
Andrew Morton <akpm@linux-foundation.org>,
Miklos Szeredi <mszeredi@suse.cz>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>, John Kacur <jkacur@redhat.com>,
linux-fsdevel@vger.kernel.org, gregf@hq.newdream.net
Subject: Re: [PATCH] fs/locks.c: prepare for BKL removal
Date: Thu, 23 Sep 2010 08:40:11 +0200 [thread overview]
Message-ID: <201009230840.11724.arnd@arndb.de> (raw)
In-Reply-To: <Pine.LNX.4.64.1009222037500.14029@cobra.newdream.net>
On Thursday 23 September 2010 05:42:49 Sage Weil wrote:
> Okay, the lock/unlock_flocks() stubs on in Linus' tree now, and the Ceph
> for-next branch is rebased and updated to fix the memory allocations and
> switch to the new interface.
Ok. I'll put the patches for the other stuff (everything but ceph and lockd)
in my bkl/vfs branch then.
> Unfortunately you still need to #include smp_lock.h for now since the
> stubs are just #defines, so we'll need to remember to clean that up later.
Don't worry about that. We have a few of those leftover ones, so we can
do a single patch removing them all before one day removing the header
file itself.
Arnd
prev parent reply other threads:[~2010-09-23 6:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 13:09 [PATCH] fs/locks.c: prepare for BKL removal Arnd Bergmann
2010-09-18 13:48 ` Matthew Wilcox
2010-09-19 19:34 ` J. Bruce Fields
2010-09-20 3:59 ` Sage Weil
2010-09-20 6:07 ` Stephen Rothwell
2010-09-21 16:12 ` Sage Weil
2010-09-21 20:09 ` Arnd Bergmann
2010-09-23 3:42 ` Sage Weil
2010-09-23 6:40 ` Arnd Bergmann [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=201009230840.11724.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=fweisbec@gmail.com \
--cc=gregf@hq.newdream.net \
--cc=hch@lst.de \
--cc=jkacur@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mszeredi@suse.cz \
--cc=sage@newdream.net \
--cc=sfr@canb.auug.org.au \
--cc=trond.myklebust@fys.uio.no \
--cc=willy@linux.intel.com \
/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).