From: Matthew Garrett <mjg59@srcf.ucam.org>
To: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dell-wmi: Change debug statements from pr_info to pr_debug
Date: Mon, 21 Nov 2011 21:18:09 +0000 [thread overview]
Message-ID: <20111121211809.GA14950@srcf.ucam.org> (raw)
In-Reply-To: <20111121211438.GH6736@thinkpad-t410>
On Mon, Nov 21, 2011 at 03:14:38PM -0600, Seth Forshee wrote:
> On Mon, Nov 21, 2011 at 08:52:30PM +0000, Matthew Garrett wrote:
> > They're intended to be there, in the same way that the keyboard code
> > generates unknown scancode errors. We want to know when users have keys
> > that don't work.
>
> All right, but what about the unknown WMI events? Those are the bigger
> problem anyway, as at least one machine (the Latitude XT2) can generate
> a lot of these messages for unknown reasons. It doesn't appear that
> anyone has been making use of these messages since we still only support
> one event. Would you object to demoting that one?
Those can probably be ignored, but again it would be nice to find out
what they actually mean so we know whether we can do anything with them.
Any chance of you being able to work with Dell on that?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-11-21 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 20:48 [PATCH] dell-wmi: Change debug statements from pr_info to pr_debug Seth Forshee
2011-11-21 20:52 ` Matthew Garrett
2011-11-21 21:10 ` Corentin Chary
2011-11-21 21:14 ` Seth Forshee
2011-11-21 21:18 ` Matthew Garrett [this message]
2011-11-21 22:29 ` Seth Forshee
2011-11-21 22:32 ` Matthew Garrett
2011-12-07 16:43 ` Seth Forshee
2011-12-07 20:22 ` Rezwanul_Kabir
2011-12-07 21:15 ` Seth Forshee
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=20111121211809.GA14950@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.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