From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Corentin Chary <corentin.chary@gmail.com>, ecc@cmu.edu
Cc: linux acpi <linux-acpi@vger.kernel.org>, linux-kernel@vger.kernel.org
Subject: [Patch 0/3] eeepc-laptop updates
Date: Mon, 17 Nov 2008 13:33:25 +0000 [thread overview]
Message-ID: <20081117133325.GB12303@srcf.ucam.org> (raw)
(This time with correct addresses...)
This patch series includes patches for the extended hotkeys on the later
Eees, tidying up some rfkill warnings and making the rfkill PCI hotplug
work correctly on the current Eees.
--
Matthew Garrett | mjg59@srcf.ucam.org
next reply other threads:[~2008-11-17 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 13:33 Matthew Garrett [this message]
2008-11-17 13:35 ` [Patch 1/3] eeepc-laptop: Add support for extended hotkeys Matthew Garrett
2008-11-17 13:38 ` [Patch 2/3] eeepc-laptop: Check return values from rfkill_register Matthew Garrett
2008-11-17 13:41 ` [Patch 3/3] eeepc-laptop: Implement rfkill hotplugging in eeepc-laptop Matthew Garrett
2008-11-17 15:09 ` [Patch 2/3] eeepc-laptop: Check return values from rfkill_register Alan Jenkins
-- strict thread matches above, loose matches on Subject: below --
2008-11-17 13:32 [Patch 0/3] eeepc-laptop updates 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=20081117133325.GB12303@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=corentin.chary@gmail.com \
--cc=ecc@cmu.edu \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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