From: Johannes Berg <johannes@sipsolutions.net>
To: Andreas Mohr <andi@lisas.de>
Cc: Bob Copeland <me@bobcopeland.com>,
linville@tuxdriver.com, maximlevitsky@gmail.com,
linux-wireless@vger.kernel.org, ath5k-devel@lists.ath5k.org
Subject: Re: [PATCH 1/2] ath5k: support LEDs on Acer Aspire One netbook
Date: Mon, 16 Mar 2009 11:16:17 +0100 [thread overview]
Message-ID: <1237198577.27769.9.camel@johannes.local> (raw)
In-Reply-To: <20090316100447.GA13819@rhlx01.hs-esslingen.de> (sfid-20090316_111434_456961_07BF0A63)
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
On Mon, 2009-03-16 at 11:04 +0100, Andreas Mohr wrote:
> On Sun, Jan 11, 2009 at 09:42:27AM -0500, Bob Copeland wrote:
> > > My LED is dead again on 2.6.29-rc1 (reason: doesn't contain this patch).
> >
> > It's in wireless-testing, it just hasn't made it through the pipeline yet.
>
> Just installed -rc8; would be truly sad to see this really small
> but important patch (several million machines) not included in .29 proper...
> (or would it later get merged via .29 -stable? Then I'm fine with it...)
I don't think "my LED doesn't blink" really counts as important...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-16 10:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 20:01 [PATCH 1/2] ath5k: support LEDs on Acer Aspire One netbook Bob Copeland
2009-01-11 13:10 ` Andreas Mohr
2009-01-11 14:42 ` Bob Copeland
2009-01-11 16:53 ` Andreas Mohr
2009-03-16 10:04 ` Andreas Mohr
2009-03-16 10:16 ` Johannes Berg [this message]
2009-03-16 10:44 ` Andreas Mohr
2009-03-16 12:21 ` Maxim Levitsky
2009-03-16 13:41 ` Andreas Mohr
2009-03-16 15:33 ` Maxim Levitsky
2009-03-16 16:00 ` Andreas Mohr
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=1237198577.27769.9.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=andi@lisas.de \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maximlevitsky@gmail.com \
--cc=me@bobcopeland.com \
/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;
as well as URLs for NNTP newsgroup(s).