From: Sujith Manoharan <sujith@msujith.org>
To: Gabor Juhos <juhosg@openwrt.org>
Cc: linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org
Subject: Re: [RFC 08/12] ath9k: Use a separate TX gain table for WZR-HP-G450H
Date: Thu, 5 Dec 2013 15:47:47 +0530 [thread overview]
Message-ID: <21152.21195.479607.597294@gargle.gargle.HOWL> (raw)
In-Reply-To: <52A05325.2070501@openwrt.org>
Gabor Juhos wrote:
> The ath9k_platform_data structure in 'include/linux/ath9k_platform.h' should be
> updated as well. Otherwise this will cause a build error.
Thanks. I'll squash patches 07 and 08 into a single one.
Sujith
next prev parent reply other threads:[~2013-12-05 10:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 8:46 [RFC 00/12] ath9k initval updates Sujith Manoharan
2013-12-05 8:46 ` [RFC 01/12] ath9k: Add initval arrays for DFS channels Sujith Manoharan
2013-12-05 8:46 ` [RFC 02/12] ath9k: Initialize baseband " Sujith Manoharan
2013-12-05 8:46 ` [RFC 03/12] ath9k: Update mac_postamble for AR9003 family Sujith Manoharan
2013-12-05 8:46 ` [RFC 04/12] ath9k: Remove AR955x INI duplicates Sujith Manoharan
2013-12-05 8:46 ` [RFC 05/12] ath9k: Update AR9331 v1.1 initvals Sujith Manoharan
2013-12-05 8:46 ` [RFC 06/12] ath9k: Update AR9331 v1.2 initvals Sujith Manoharan
2013-12-05 8:46 ` [RFC 07/12] ath9k: Add a new flag for Buffalo devices Sujith Manoharan
2013-12-05 8:46 ` [RFC 08/12] ath9k: Use a separate TX gain table for WZR-HP-G450H Sujith Manoharan
2013-12-05 10:19 ` Gabor Juhos
2013-12-05 10:17 ` Sujith Manoharan [this message]
2013-12-05 10:34 ` Gabor Juhos
2013-12-05 8:46 ` [RFC 09/12] ath9k: Update high power gain table for AR9300 Sujith Manoharan
2013-12-05 8:46 ` [RFC 10/12] ath9k: Identify duplicate AR9485 initvals Sujith Manoharan
2013-12-05 8:46 ` [RFC 11/12] ath9k: Identify duplicate AR9462 v2.0 initvals Sujith Manoharan
2013-12-05 8:46 ` [RFC 12/12] ath9k: Identify duplicate AR9565 v1.0 initvals Sujith Manoharan
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=21152.21195.479607.597294@gargle.gargle.HOWL \
--to=sujith@msujith.org \
--cc=ath9k-devel@lists.ath9k.org \
--cc=juhosg@openwrt.org \
--cc=linux-wireless@vger.kernel.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