linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Florian Fainelli <florian@openwrt.org>
Cc: "Luis R. Rodriguez" <lrodriguez@qca.qualcomm.com>,
	linux-wireless@vger.kernel.org, nbd@openwrt.org
Subject: Re: [PATCH] ath9k: add missing AR9340 in ath_mac_bb_names
Date: Tue, 30 Aug 2011 13:48:11 -0400	[thread overview]
Message-ID: <20110830174810.GA2660@tuxdriver.com> (raw)
In-Reply-To: <201108301101.27843.florian@openwrt.org>

On Tue, Aug 30, 2011 at 11:01:27AM +0200, Florian Fainelli wrote:
> Luis, John,
> 
> On Thursday 25 August 2011 21:33:48 Florian Fainelli wrote:
> > AR9340 is not listed in ath_mac_bb_names, which leads to such a message:
> > ieee80211 phy0: Atheros AR???? Rev:0 mem=0xb8100000, irq=2
> > 
> > Signed-off-by: Florian Fainelli <florian@openwrt.org>
> 
> Can you pick this up? Thanks.

Did you actually check to see if it had been merged into wireless-next?

commit 397e5d5b93ba99ad3dc56f1e294f487e77d2daa8
Author: Florian Fainelli <florian@openwrt.org>
Date:   Thu Aug 25 21:33:48 2011 +0200

    ath9k: add missing AR9340 in ath_mac_bb_names
    
    AR9340 is not listed in ath_mac_bb_names, which leads to such a message:
    ieee80211 phy0: Atheros AR???? Rev:0 mem=0xb8100000, irq=2
    
    Signed-off-by: Florian Fainelli <florian@openwrt.org>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2011-08-30 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25 19:33 [PATCH] ath9k: add missing AR9340 in ath_mac_bb_names Florian Fainelli
2011-08-30  9:01 ` Florian Fainelli
2011-08-30 17:48   ` John W. Linville [this message]
2011-08-30 18:08     ` Florian Fainelli

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=20110830174810.GA2660@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=florian@openwrt.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@qca.qualcomm.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).