From: Nick Bowler <nbowler@elliptictech.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/4] BKL: move CONFIG_BKL to staging
Date: Wed, 19 Jan 2011 10:44:19 -0500 [thread overview]
Message-ID: <20110119154419.GA21411@elliptictech.com> (raw)
In-Reply-To: <1295385422-3592-5-git-send-email-arnd@arndb.de>
On 2011-01-18 22:17 +0100, Arnd Bergmann wrote:
> Instead of moving the actual code to staging for stuff that
> depends on CONFIG_BKL, this moves just the configuration
> option it depends on.
>
> As a consequence, the remaining non-staging drivers that use
> the BKL (i830, appletalk, ipx, x25, adfs, hpfs and ufs)
> implicitly depend on staging until they get fixed.
>
> This sets 2.6.39 as the arbitrary date when we actually remove
> the option along with its last users.
I think this patch is not very nice. It will cause working kernel
configurations to turn into broken kernel configurations when the user
does 'make oldconfig', with no warning.
These drivers that use the BKL work fine. Removing working features
with no adequate replacement available seems like a serious regression
to me.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2011-01-19 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 21:16 [PATCH 0/4] Phasing out the BKL Arnd Bergmann
2011-01-18 21:16 ` [PATCH 1/4] drm/i810: remove " Arnd Bergmann
2011-01-18 21:17 ` [PATCH 2/4] BKL: disable by default Arnd Bergmann
2011-01-18 21:17 ` [PATCH 3/4] BKL: mark lock_kernel as deprecated Arnd Bergmann
2011-01-18 21:17 ` [PATCH 4/4] BKL: move CONFIG_BKL to staging Arnd Bergmann
2011-01-19 15:44 ` Nick Bowler [this message]
2011-01-19 16:17 ` Arnd Bergmann
2011-01-19 18:21 ` Nick Bowler
2011-01-23 22:19 ` Andrew Hendry
[not found] ` <AANLkTimOzU328aHnB7+ERSq1ovPBSZgxNQsYRhLghH5L@mail.gmail.com>
2011-01-24 15:59 ` Arnd Bergmann
2011-01-25 0:33 ` Andrew Hendry
2011-01-25 12:06 ` 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=20110119154419.GA21411@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--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