From: Bob Copeland <me@bobcopeland.com>
To: Keng-Yu Lin <keng-yu.lin@canonical.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ath5k: add LED support for Acer Aspire One AO751h/AO531h
Date: Wed, 4 Nov 2009 21:59:39 -0500 [thread overview]
Message-ID: <b6c5339f0911041859v762f90f4u1b369a80841ea756@mail.gmail.com> (raw)
In-Reply-To: <1257389729-26491-1-git-send-email-keng-yu.lin@canonical.com>
On Wed, Nov 4, 2009 at 9:55 PM, Keng-Yu Lin <keng-yu.lin@canonical.com> wrote:
> Add LED support for a Foxconn AR242X module, found on
> the Acer Aspire One models AO751h/AO531h
>
> Signed-off-by: Keng-Yu Lin <keng-yu.lin@canonical.com>
> ---
> drivers/net/wireless/ath/ath5k/led.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath5k/led.c b/drivers/net/wireless/ath/ath5k/led.c
> index b767c3b..21a42a1 100644
> --- a/drivers/net/wireless/ath/ath5k/led.c
> +++ b/drivers/net/wireless/ath/ath5k/led.c
> @@ -59,6 +59,8 @@ static const struct pci_device_id ath5k_led_devices[] = {
> { ATH_SDEVICE(PCI_VENDOR_ID_COMPAQ, PCI_ANY_ID), ATH_LED(1, 1) },
> /* Acer Aspire One A150 (maximlevitsky@gmail.com) */
> { ATH_SDEVICE(PCI_VENDOR_ID_FOXCONN, 0xe008), ATH_LED(3, 0) },
> + /* Acer Aspire One AO531h AO751h */
> + { ATH_SDEVICE(PCI_VENDOR_ID_FOXCONN, 0xe00d), ATH_LED(3, 0) },
Acked-by: Bob Copeland <me@bobcopeland.com>
... but can you by chance put a contact address in the comment? I've been
collecting them in case we one day figure out a better way to do this so it's
easy to find the people to retest.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-11-05 2:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 2:55 [PATCH] ath5k: add LED support for Acer Aspire One AO751h/AO531h Keng-Yu Lin
2009-11-05 2:59 ` Bob Copeland [this message]
2009-11-05 3:21 ` Keng-Yu Lin
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=b6c5339f0911041859v762f90f4u1b369a80841ea756@mail.gmail.com \
--to=me@bobcopeland.com \
--cc=keng-yu.lin@canonical.com \
--cc=linux-wireless@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