From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sage Weil <sage@newdream.net>,
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: Mon, 20 Sep 2010 16:07:29 +1000 [thread overview]
Message-ID: <20100920160729.96872d12.sfr@canb.auug.org.au> (raw)
In-Reply-To: <Pine.LNX.4.64.1009192009260.9243@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
On Sun, 19 Sep 2010 20:59:01 -0700 (PDT) Sage Weil <sage@newdream.net> wrote:
>
> I suspect the easiest thing is to leave Ceph out of this stage of your
> series, I'll switch lock_kernel() to lock_flocks() once that exists
> upstream. Unless there is a better way?
Maybe someone could write a trivial implementation of lock_flocks() (i.e.
one that does not make any changes to behaviour) and ask Linus to take it
now in preparation for the next merge window (he has done that before).
That way, more of this could be put into individual other trees and avoid
more conflicts ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-09-20 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 13:09 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 [this message]
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
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=20100920160729.96872d12.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--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=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
all inboxes | Powered by JetHome®