From: Pavel Roskin <proski@gnu.org>
To: Gabor Juhos <juhosg@openwrt.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
Jouni Malinen <jmalinen@atheros.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@venema.h4ckr.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Felix Fietkau <nbd@openwrt.org>,
Christoph Hellwig <hch@infradead.org>,
Sujith Manoharan <Sujith.Manoharan@atheros.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH v3 00/11] ath9k: add preliminary support for the AR913x SoCs
Date: Tue, 13 Jan 2009 16:38:51 -0500 [thread overview]
Message-ID: <1231882731.21706.10.camel@dv> (raw)
In-Reply-To: <1231854029-26810-1-git-send-email-juhosg@openwrt.org>
On Tue, 2009-01-13 at 14:40 +0100, Gabor Juhos wrote:
> This patch set introduces preliminary support for the Atheros' AR9130/AR9132
> SoCs built-in WMAC device. Tested with compat-wireless-2009-01-12 and 2.6.27.10
> kernel on the following devices:
> * Atheros AP83-050 reference board (AR9132 SoC, AR9106 RF)
> * TRENDnet TEW-632BRP router (AR9130 SoC, AR9102 RF)
> * Mikrotik RB433 board (AR7161 SoC) + AR5416 based miniPCI card
I confirm that my AR5416 miniPCI is still working with this patch on top
of yesterdays wireless-testing (master-2009-01-12).
Unfortunately, patch named "ath9k: move PCI code into separate file"
doesn't apply to the today's wireless-testing and needs to be rebased.
Current checkpatch.pl gets confused by several patches because an
"#endif" in the unchanged part somehow causes the preprocessor stack to
underflow:
Can't use an undefined value as an ARRAY reference at
scripts/checkpatch.pl line 453.
This appears to be a bug in checkpatch.pl and should not be considered a
problem in the patches.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-01-13 21:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 13:40 [PATCH v3 00/11] ath9k: add preliminary support for the AR913x SoCs Gabor Juhos
2009-01-13 13:40 ` [PATCH v3 01/11] ath9k: convert to struct device Gabor Juhos
2009-01-13 13:40 ` [PATCH v3 02/11] ath9k: convert to use bus-agnostic DMA routines Gabor Juhos
2009-01-13 13:40 ` [PATCH v3 03/11] ath9k: introduce bus specific cache size routine Gabor Juhos
2009-01-13 13:40 ` [PATCH v3 04/11] ath9k: introduce bus specific cleanup routine Gabor Juhos
2009-01-13 13:40 ` [PATCH v3 05/11] ath9k: move PCI code into separate file Gabor Juhos
2009-01-13 13:40 ` [PATCH v3 06/11] ath9k: introduce platform driver for AHB bus support Gabor Juhos
2009-01-13 13:40 ` [PATCH v3 07/11] ath9k: get EEPROM contents from platform data on AHB bus Gabor Juhos
2009-01-13 13:40 ` [PATCH v3 08/11] ath9k: remove (u16) casts from rtc register access Gabor Juhos
2009-01-13 13:40 ` [PATCH v3 09/11] ath9k: fix ar5416Addac_9100 values Gabor Juhos
2009-01-13 13:40 ` [PATCH v3 10/11] ath9k: fix null pointer dereference in ani monitor code Gabor Juhos
2009-01-13 13:40 ` [PATCH v3 11/11] ath9k: enable support for AR9100 Gabor Juhos
2009-01-13 21:38 ` Pavel Roskin [this message]
2009-01-14 19:15 ` [PATCH v3 00/11] ath9k: add preliminary support for the AR913x SoCs Gabor Juhos
2009-01-14 22:02 ` Pavel Roskin
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=1231882731.21706.10.camel@dv \
--to=proski@gnu.org \
--cc=Sujith.Manoharan@atheros.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=hch@infradead.org \
--cc=jmalinen@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=juhosg@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=nbd@openwrt.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).