From: Gabor Juhos <juhosg@openwrt.org>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: Sangwook Lee <sangwook.lee@linaro.org>,
Imre Kaloz <kaloz@openwrt.org>,
linux-kernel@vger.kernel.org, linux-mips@linux-mips.org,
linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org,
ralf@linux-mips.org, linville@tuxdriver.com,
rmanohar@qca.qualcomm.com, patches@linaro.org
Subject: Re: [PATCH] ath9k: rename ath9k_platform.h to ath_platform.h
Date: Wed, 16 Nov 2011 22:11:51 +0100 [thread overview]
Message-ID: <4EC42717.2050806@openwrt.org> (raw)
In-Reply-To: <CAB=NE6UB6KzJ2p+sou4wcgnZ9jyQxhpWMr2qZ2=jwqaGc2L5Xw@mail.gmail.com>
2011.11.15. 17:09 keltezéssel, Luis R. Rodriguez írta:
> 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?
It is used by the ath79 platform code in the mainline kernel, although only the
AP81 reference board uses that for now. However the linux-mips tree also has
code for the AP121 reference board, and that will use it as well.
Additionaly, we are using that in OpenWrt for several consumer boards which are
based on the AR71xx/AR724x/AR913x SoCs.
-Gabor
next prev parent reply other threads:[~2011-11-16 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 11:23 [PATCH] ath9k: rename ath9k_platform.h to ath_platform.h Sangwook Lee
2011-11-15 16:09 ` Luis R. Rodriguez
2011-11-16 21:11 ` Gabor Juhos [this message]
2011-11-15 16:37 ` Kalle Valo
[not found] ` <CADPsn1YDOu9Xyu1yDfs5Z0LjGzBL-Rx6Fk35AT8n-8oOPhPzHA@mail.gmail.com>
2011-11-17 19:06 ` Kalle Valo
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=4EC42717.2050806@openwrt.org \
--to=juhosg@openwrt.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=kaloz@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@frijolero.org \
--cc=patches@linaro.org \
--cc=ralf@linux-mips.org \
--cc=rmanohar@qca.qualcomm.com \
--cc=sangwook.lee@linaro.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;
as well as URLs for NNTP newsgroup(s).