From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Mario Limonciello <superm1@ubuntu.com>
Cc: 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 22:24:51 +0100 [thread overview]
Message-ID: <20101007212451.GA1458@srcf.ucam.org> (raw)
In-Reply-To: <AANLkTi=bj3T5hcX9r3j5kyEQkNb7PAZK948kcrx4R8tC@mail.gmail.com>
On Thu, Oct 07, 2010 at 03:53:37PM -0500, Mario Limonciello wrote:
> Yes the issue is the firmware's response to the keystroke. The
> intention here is to individual submit machines in future patches as
> they're discovered. The parameter's primary purpose is to assist in
> building the list. If someone reports a bug with these symptoms, they
> can add the parameter to their kernel command line, and report if it
> helps them. If it helps, their machine can be added to the DMI table.
Sorry, I'm not adding this as a module option. How can you not know
which machines are affected?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-10-07 21:24 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 [this message]
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
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=20101007212451.GA1458@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=keng-yu.lin@canonical.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.