From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
<ath9k-devel@lists.ath9k.org>, <linux-wireless@vger.kernel.org>,
Rodriguez Luis <rodrigue@qca.qualcomm.com>
Subject: Re: [ath9k-devel] [RFC] ath9k_hw: Fix chip revision checks
Date: Mon, 12 Mar 2012 14:46:04 +0530 [thread overview]
Message-ID: <4F5DBED4.4050500@qca.qualcomm.com> (raw)
In-Reply-To: <4F5DBB8B.1070000@openwrt.org>
Hi Felix,
On Monday 12 March 2012 02:32 PM, Felix Fietkau wrote:
> On 2012-03-12 6:57 AM, Mohammed Shafi Shajakhan wrote:
>> From: Mohammed Shafi Shajakhan<mohammed@qca.qualcomm.com>
>>
>> not sure if these checks are previously avoided may be those revision of
>> chipsets are obselete ?
> NACK. The extra checks that this patch adds have been intentionally
> removed, since all earlier versions were never sold and thus do not need
> to be considered. This simplifies the generated binary code.
IMHO i don't think this patch does anything wrong to deserve a NACK!
sometimes these optimizations make it tad difficult if we want to
quickly check with the HAL code.
true i just found from the commit
ath9k_hw: simplify revision checks for AR9280
Since AR9280 v1.0 was never sold (and the initvals removed), v1.0
specific
revision checks can be removed and the 'v2.0 or later' check can be
simplified to a check for AR9280 or later.
while adding some new code while AR_9280_SREV_20 later was not in
uniform with the other chipset macros. i should have just checked with
git annotate reg.h could have found your commit.
thanks for the review!
>
> - Felix
--
thanks,
shafi
next prev parent reply other threads:[~2012-03-12 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 5:57 [RFC] ath9k_hw: Fix chip revision checks Mohammed Shafi Shajakhan
2012-03-12 9:02 ` [ath9k-devel] " Felix Fietkau
2012-03-12 9:16 ` Mohammed Shafi Shajakhan [this message]
2012-03-12 9:41 ` Mohammed Shafi Shajakhan
2012-03-12 20:16 ` Luis R. Rodriguez
2012-03-13 4:36 ` Mohammed Shafi Shajakhan
2012-03-12 9:44 ` Mohammed Shafi Shajakhan
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=4F5DBED4.4050500@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=nbd@openwrt.org \
--cc=rodrigue@qca.qualcomm.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;
as well as URLs for NNTP newsgroup(s).