linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Sujith <Sujith.Manoharan@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	Vasanth.Thiagarajan@Atheros.com,
	Senthilkumar.Balasubramanian@Atheros.com
Subject: Re: [PATCH] ath9k_htc: Add ath9k_htc driver
Date: Fri, 26 Feb 2010 13:33:21 -0500	[thread overview]
Message-ID: <1267209201.30426.8.camel@mj> (raw)
In-Reply-To: <19335.43241.887933.207404@gargle.gargle.HOWL>

On Fri, 2010-02-26 at 16:26 +0530, Sujith wrote:

> Support for AR9271 chipset.

Great news!!!

> --- a/drivers/net/wireless/ath/ath9k/calib.h
> +++ b/drivers/net/wireless/ath/ath9k/calib.h
> @@ -114,6 +114,7 @@ struct ath9k_nfcal_hist {
>  };
>  
>  #define MAX_PACAL_SKIPCOUNT 8
> +
>  struct ath9k_pacal_info{

You may want to omit this part ;-)

> @@ -1240,7 +1228,7 @@ void ath9k_hw_deinit(struct ath_hw *ah)
>  {
>  	struct ath_common *common = ath9k_hw_common(ah);
>  
> -	if (common->state <= ATH_HW_INITIALIZED)
> +	if (common->state < ATH_HW_INITIALIZED)
>  		goto free_hw;
>  
>  	if (!AR_SREV_9100(ah))

There are some non-trivial parts like this one that could be submitted
separately.

> @@ -1249,10 +1237,8 @@ void ath9k_hw_deinit(struct ath_hw *ah)
>  	ath9k_hw_setpower(ah, ATH9K_PM_FULL_SLEEP);
>  
>  free_hw:
> -	if (!AR_SREV_9280_10_OR_LATER(ah))
> +	if (!AR_SREV_9280_10_OR_LATER(ah) && !AR_SREV_9271(ah))
>  		ath9k_hw_rf_free_ext_banks(ah);
> -	kfree(ah);
> -	ah = NULL;

Another one.  Actually, it is trivial, but not ath9k_htc related.

It would be really nice to fast track the ath9k_htc driver to 2.6.34,
but the changes affecting other devices should be separate, I believe.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2010-02-26 18:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 10:56 [PATCH] ath9k_htc: Add ath9k_htc driver Sujith
2010-02-26 18:33 ` Pavel Roskin [this message]
2010-02-26 18:42   ` Luis R. Rodriguez
2010-02-27  1:19     ` Pavel Roskin
2010-02-27  5:29       ` Sujith
2010-03-06 15:27         ` Kalle Valo
2010-03-06 15:54           ` John W. Linville
2010-02-27  6:09     ` Sujith
2010-02-27  5:24   ` Sujith

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=1267209201.30426.8.camel@mj \
    --to=proski@gnu.org \
    --cc=Senthilkumar.Balasubramanian@Atheros.com \
    --cc=Sujith.Manoharan@atheros.com \
    --cc=Vasanth.Thiagarajan@Atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).