From: Kalle Valo <kalle.valo@iki.fi>
To: Christian Lamparter <chunkeey@web.de>
Cc: Michael Buesch <mb@bu3sch.de>,
Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] p54: fix SoftLED compile dependencies
Date: Sat, 21 Mar 2009 14:27:49 +0200 [thread overview]
Message-ID: <873ad7dpru.fsf@litku.valot.fi> (raw)
In-Reply-To: <200903211322.01654.chunkeey@web.de> (Christian Lamparter's message of "Sat\, 21 Mar 2009 13\:22\:01 +0100")
Christian Lamparter <chunkeey@web.de> writes:
>> > - Inventel UR054G
>> > - Spinnaker DUT
>>
>> This change wasn't mentioned in the commit log. Did this get included
>> by accident?
>>
> heh true... should I add them back?
I don't know, I just wanted to point this out in case you missed it :)
> after all this list hasn't changed in years and we have a much nicer
> one on http://www.prism54.org/ (
> http://wireless.kernel.org/en/users/Drivers/p54/devices )
In my opinion wireless.kernel.org is better place for the list.
--
Kalle Valo
next prev parent reply other threads:[~2009-03-21 12:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090319221024.5e2ad6e5.sfr@canb.auug.org.au>
2009-03-19 17:28 ` linux-next: Tree for March 19 (wireless/p54) Randy Dunlap
2009-03-19 17:50 ` Michael Buesch
2009-03-19 18:49 ` Randy Dunlap
2009-03-19 18:55 ` Michael Buesch
2009-03-20 23:57 ` [PATCH] p54: fix SoftLED compile dependencies Christian Lamparter
2009-03-21 6:36 ` Kalle Valo
2009-03-21 12:22 ` Christian Lamparter
2009-03-21 12:27 ` Kalle Valo [this message]
2009-03-21 15:26 ` Larry Finger
2009-03-23 14:13 ` John W. Linville
2009-03-23 14:37 ` [PATCH v2] " Christian Lamparter
2009-03-23 1:00 ` [PATCH] " Randy Dunlap
2009-03-23 14:14 ` John W. Linville
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=873ad7dpru.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=chunkeey@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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).