[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=qvOHwgsbaCO6_Eu2Uik7MP5=C64+WW8R-RR8B@mail.gmail.com>
Date: Sun, 21 Nov 2010 09:45:12 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Boaz Harrosh <openosd@...il.com>
Cc: Jan Kara <jack@...e.cz>, Arnd Bergmann <arnd@...db.de>,
linux-kernel@...r.kernel.org, Nathan Laredo <laredo@....org>,
Greg Kroah-Hartman <gregkh@...e.de>,
Dave Airlie <airlied@...ux.ie>,
dri-devel@...ts.freedesktop.org,
"J. Bruce Fields" <bfields@...ldses.org>,
linux-nfs@...r.kernel.org,
Alessio Igor Bogani <alessioigorbogani@...il.com>
Subject: Re: [PATCH 0/7] BKL removal follow-up
On Sun, Nov 21, 2010 at 6:12 AM, Boaz Harrosh <openosd@...il.com> wrote:
> On 11/19/2010 01:40 AM, Linus Torvalds wrote:
>>
>> I don't think I can reasonably do it in 37, we're late enough in the
>> -rc series. So UDF and really saying 'n' to BKL by default will have
>> to be for the next merge window.
>
> Could it not default to "n" but be SELECTed by the like of UDF. Or
> that too big of a Kconfig change for 37-rcX? I understand it does
> not really buy us anything for distro's with allmodconfig style,
> but it should help with defconfig on all the other ARCH's.
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.
Tested patch?
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists