From: Daniel Golle <dgolle@allnet.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: rename ath9k_platform.h to ath_platform.h
Date: Tue, 15 Nov 2011 17:28:20 +0100 [thread overview]
Message-ID: <4EC29324.3040004@allnet.de> (raw)
In-Reply-To: <CAB=NE6UB6KzJ2p+sou4wcgnZ9jyQxhpWMr2qZ2=jwqaGc2L5Xw@mail.gmail.com>
On 11/15/2011 05:09 PM, Luis R. Rodriguez wrote:
> On Tue, Nov 15, 2011 at 3:23 AM, Sangwook Lee <sangwook.lee@linaro.org> wrote:
>> The patch series proposes to rename ath9k_platform.h to "ath_platform.h
>> This header file handles platform data used only for ath9k,
>> but it can used by ath6k as well.
> Adding the actual OpenWrt stakeholders. Is there any public hardware
> platform that uses this yet?
Same for ath5k, after discussing the issue on openwrt-devel (in June 2010) we
decided to have a seperate _platform struct for each chip. However, I agree that
this is unneeded redundancy and it would be nice to have things generalized in a
single ath_platform.h.
The ALL0305 (based on Senao eap7660d board) currently uses ath5k_platform.
Cheers
Daniel
next prev parent reply other threads:[~2011-11-15 16:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 11:23 [ath9k-devel] [PATCH] ath9k: rename ath9k_platform.h to ath_platform.h Sangwook Lee
2011-11-15 11:23 ` Sangwook Lee
2011-11-15 11:23 ` Sangwook Lee
2011-11-15 16:09 ` [ath9k-devel] " Luis R. Rodriguez
2011-11-15 16:09 ` Luis R. Rodriguez
2011-11-15 16:09 ` Luis R. Rodriguez
2011-11-15 16:28 ` Daniel Golle [this message]
2011-11-16 21:11 ` [ath9k-devel] " Gabor Juhos
2011-11-16 21:11 ` Gabor Juhos
2011-11-16 21:11 ` Gabor Juhos
2011-11-15 16:37 ` [ath9k-devel] " Kalle Valo
2011-11-15 16:37 ` Kalle Valo
2011-11-15 16:37 ` Kalle Valo
2011-11-16 11:34 ` [ath9k-devel] " Sangwook Lee
2011-11-17 19:06 ` Kalle Valo
2011-11-17 19:06 ` Kalle Valo
2011-11-17 19:06 ` Kalle Valo
2011-11-17 19:06 ` Kalle Valo
2011-11-22 9:17 ` [ath9k-devel] " Sangwook Lee
2011-11-22 9:17 ` Sangwook Lee
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=4EC29324.3040004@allnet.de \
--to=dgolle@allnet.de \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.