Linux wireless drivers development
 help / color / mirror / Atom feed
From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: <linville@tuxdriver.com>, <linux-wireless@vger.kernel.org>,
	<ath9k-devel@lists.ath9k.org>
Subject: Re: [PATCH 3/4] ath9k: Modify CCK spur mitigation for AR9462
Date: Tue, 14 Feb 2012 14:53:30 +0530	[thread overview]
Message-ID: <20282.10258.858715.688562@gargle.gargle.HOWL> (raw)
In-Reply-To: <CAD2nsn3sVaAea1iBRAgp7-j733BznjrB6sU_i5V1SZ0_kpC1fA@mail.gmail.com>

Mohammed Shafi wrote:
> i saw this some time back ,the check will not take care of this logic
> 
> if (AR_SREV_9462(ah) && (i == 0 || i == 3))
> 			continue;

Yep, looks like this is already handled. Thanks for catching this.

Sujith

      reply	other threads:[~2012-02-14  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14  8:39 [PATCH 3/4] ath9k: Modify CCK spur mitigation for AR9462 Sujith Manoharan
2012-02-14  9:07 ` Mohammed Shafi
2012-02-14  9:23   ` Sujith Manoharan [this message]

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=20282.10258.858715.688562@gargle.gargle.HOWL \
    --to=c_manoha@qca.qualcomm.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=shafi.wireless@gmail.com \
    /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