From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Mario Limonciello <superm1@ubuntu.com>,
Keng-Yu Lin <keng-yu.lin@canonical.com>,
len.brown@intel.com, alan-jenkins@tuffmail.co.uk,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dell-laptop: Add hwswitch_only module parameter
Date: Thu, 7 Oct 2010 14:58:54 -0700 [thread overview]
Message-ID: <20101007215854.GC18628@core.coreip.homeip.net> (raw)
In-Reply-To: <20101007215028.GB2292@srcf.ucam.org>
On Thu, Oct 07, 2010 at 10:50:28PM +0100, Matthew Garrett wrote:
> On Thu, Oct 07, 2010 at 02:46:28PM -0700, Dmitry Torokhov wrote:
> > On Thu, Oct 07, 2010 at 10:37:54PM +0100, Matthew Garrett wrote:
> > > Dell laptop driver is reasonable. All we need is a list of hardware, and
> > > I'd really hope that Dell know which BIOS versions contain this code!
> > >
> >
> > Unfortunately this kind of crap tends to flow from one BIOS version to
> > another.. How many DMI entries do we know about so far? Did Dell issue
> > firmware updates correcting the issue so new boxes will not exhibit the
> > problem?
>
> Pushing this out to userspace doesn't help. If it's sufficiently
> prevelant that it's impossible to have a comprehensive list, then a
> module option makes it too easy for people to just post the fix on a
> forum somewhere and never actually get it upstream.
>
Forcing users patching the kernel reduces chances that it will be fixed
at all. Also there is load of patches that never make into distributions
and even less in mainline. Or if they make it it takes looong time...
so I do not think it is a valid argument here.
--
Dmitry
prev parent reply other threads:[~2010-10-07 21:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 3:30 [PATCH] dell-laptop: Add hwswitch_only module parameter Keng-Yu Lin
2010-10-07 11:15 ` Matthew Garrett
[not found] ` <AANLkTinus8SxbXt14qabXgpbFXF4U+uNoKA-=eDuOjmp@mail.gmail.com>
2010-10-07 13:35 ` Matthew Garrett
2010-10-07 20:49 ` Mario Limonciello
2010-10-07 20:50 ` Matthew Garrett
2010-10-07 20:53 ` Mario Limonciello
2010-10-07 21:24 ` Matthew Garrett
2010-10-07 21:30 ` Dmitry Torokhov
2010-10-07 21:33 ` Mario Limonciello
2010-10-07 21:37 ` Matthew Garrett
2010-10-07 21:41 ` Mario Limonciello
2010-10-07 21:42 ` Matthew Garrett
2010-10-07 21:45 ` Mario Limonciello
2010-10-07 21:49 ` Matthew Garrett
2010-10-07 21:52 ` Mario Limonciello
2010-10-07 21:46 ` Dmitry Torokhov
2010-10-07 21:49 ` Mario Limonciello
2010-10-07 21:50 ` Matthew Garrett
2010-10-07 21:57 ` Mario Limonciello
2010-10-07 21:58 ` Dmitry Torokhov [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=20101007215854.GC18628@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=keng-yu.lin@canonical.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=superm1@ubuntu.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