From: Nick Bowler <nbowler@elliptictech.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Boaz Harrosh <openosd@gmail.com>, Jan Kara <jack@suse.cz>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, Nathan Laredo <laredo@gnu.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Dave Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
"J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org,
Alessio Igor Bogani <alessioigorbogani@gmail.com>
Subject: Re: [PATCH 0/7] BKL removal follow-up
Date: Mon, 22 Nov 2010 10:17:23 -0500 [thread overview]
Message-ID: <20101122151723.GA8732@elliptictech.com> (raw)
In-Reply-To: <AANLkTi=qvOHwgsbaCO6_Eu2Uik7MP5=C64+WW8R-RR8B@mail.gmail.com>
On 2010-11-21 09:45 -0800, Linus Torvalds wrote:
> Yes, I'd be ok with UDF doing a "select BKL" along with a "default n"
> for BKL itself.
>
> I think UDF currently is the only sane reason to have BKL enabled any
> more, and yes, it would probably make it easier to configure things.
UFS (which I use) also relies on BKL.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
prev parent reply other threads:[~2010-11-22 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 15:26 [PATCH 0/7] BKL removal follow-up Arnd Bergmann
2010-11-17 15:26 ` [PATCH 4/7] BKL: remove references to lock_kernel from comments Arnd Bergmann
2010-11-17 15:40 ` J. Bruce Fields
2010-11-18 23:34 ` [PATCH 0/7] BKL removal follow-up Jan Kara
2010-11-18 23:40 ` Linus Torvalds
2010-11-21 14:12 ` Boaz Harrosh
2010-11-21 17:45 ` Linus Torvalds
2010-11-22 15:17 ` Nick Bowler [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=20101122151723.GA8732@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=airlied@linux.ie \
--cc=alessioigorbogani@gmail.com \
--cc=arnd@arndb.de \
--cc=bfields@fieldses.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@suse.de \
--cc=jack@suse.cz \
--cc=laredo@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=openosd@gmail.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).