From: Thomas Renninger <trenn@suse.de>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: mjg59@srcf.ucam.org, platform-driver-x86@vger.kernel.org,
Carlos Corbacho <carlos@strangeworlds.co.uk>
Subject: Re: [PATCH 1/3] X86 platform wmi: Introduce debug param to log all WMI events
Date: Tue, 4 May 2010 14:43:12 +0200 [thread overview]
Message-ID: <201005041443.13608.trenn@suse.de> (raw)
In-Reply-To: <q2g71cd59b01005040454xde9c0aabq3d997f8ef157891c@mail.gmail.com>
On Tuesday 04 May 2010 01:54:44 pm Corentin Chary wrote:
> On Mon, May 3, 2010 at 3:30 PM, Thomas Renninger <trenn@suse.de> wrote:
> > To give people easily an idea what could be WMI driven on their system.
...
> CCing wmi.c maintainer.
Oh dear, I mixed you up. Both starting with C.. C.. :)
Corentin: Do you read platform-driver-x86@vger.kernel.org?
I'll bounce you the three patches...
Thomas
next prev parent reply other threads:[~2010-05-04 12:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 13:30 [PATCH 1/3] X86 platform wmi: Introduce debug param to log all WMI events Thomas Renninger
2010-05-03 13:30 ` [PATCH 2/3] X86 platform wmi: Also log GUID string when an event happens and debug is set Thomas Renninger
2010-05-04 17:39 ` Carlos Corbacho
2010-05-03 13:30 ` [PATCH 3/3] X86 platfrom wmi: Add debug facility to dump WMI data in a readable way Thomas Renninger
2010-05-04 17:40 ` Carlos Corbacho
2010-05-05 10:53 ` Thomas Renninger
2010-05-04 11:54 ` [PATCH 1/3] X86 platform wmi: Introduce debug param to log all WMI events Corentin Chary
2010-05-04 12:43 ` Thomas Renninger [this message]
2010-05-04 13:22 ` Corentin Chary
2010-05-04 17:39 ` Carlos Corbacho
2010-05-20 13:37 ` Matthew Garrett
2010-05-20 13:42 ` Matthew Garrett
2010-05-20 14:35 ` Thomas Renninger
2010-05-20 14:37 ` Matthew Garrett
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=201005041443.13608.trenn@suse.de \
--to=trenn@suse.de \
--cc=carlos@strangeworlds.co.uk \
--cc=corentin.chary@gmail.com \
--cc=mjg59@srcf.ucam.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 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.