From: Len Brown <lenb@kernel.org>
To: Corentin Chary <corentincj@iksaif.net>
Cc: linux-acpi@vger.kernel.org, Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Subject: Re: [PATCH 3/7] eeepc-laptop: Work around rfkill firmware bug
Date: Thu, 14 May 2009 11:21:53 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0905141121490.19537@localhost.localdomain> (raw)
In-Reply-To: <1240817023-5985-4-git-send-email-corentincj@iksaif.net>
applied
thanks,
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-05-14 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1240817023-5985-1-git-send-email-corentincj@iksaif.net>
[not found] ` <1240817023-5985-2-git-send-email-corentincj@iksaif.net>
2009-05-14 15:15 ` [PATCH 1/7] eeepc-laptop: fix wlan rfkill state change during init Len Brown
[not found] ` <1240817023-5985-3-git-send-email-corentincj@iksaif.net>
2009-05-14 15:19 ` [PATCH 2/7] eeepc-laptop: report brightness control events via the input layer Len Brown
[not found] ` <1240817023-5985-4-git-send-email-corentincj@iksaif.net>
2009-05-14 15:21 ` Len Brown [this message]
[not found] ` <1240817023-5985-5-git-send-email-corentincj@iksaif.net>
2009-05-14 15:23 ` [PATCH 4/7] eeepc-laptop: support for super hybrid engine (SHE) Len Brown
[not found] ` <1240817023-5985-6-git-send-email-corentincj@iksaif.net>
[not found] ` <1240817023-5985-7-git-send-email-corentincj@iksaif.net>
2009-05-14 15:27 ` [PATCH 6/7] asus-laptop: fix input keycode Len Brown
[not found] ` <1240817023-5985-8-git-send-email-corentincj@iksaif.net>
2009-05-14 15:28 ` [PATCH 7/7] eeepc-laptop: unregister_rfkill_notifier on failure Len Brown
2009-05-14 15:33 ` [PATCH 5/7] eeepc-laptop: Register as a pci-hotplug device Len Brown
2009-05-15 9:31 ` Corentin Chary
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=alpine.LFD.2.00.0905141121490.19537@localhost.localdomain \
--to=lenb@kernel.org \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=corentincj@iksaif.net \
--cc=linux-acpi@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