mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: Joe Perches <joe@perches.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
	Nick Kossifidis <mickflemm@gmail.com>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	Bob Copeland <me@bobcopeland.com>,
	Jouni Malinen <jmalinen@atheros.com>,
	Vasanthakumar Thiagarajan <vasanth@atheros.com>,
	Senthil Balasubramanian <senthilkumar@atheros.com>,
	netdev@vger.kernel.org, ath5k-devel@venema.h4ckr.net,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-kernel@vger.kernel.org, ath9k-devel@venema.h4ckr.net
Subject: Re: [ath9k-devel] [PATCH 2/2] ath: Fix logging message typos
Date: Thu, 2 Dec 2010 06:30:54 +0100	[thread overview]
Message-ID: <20101202053055.19479.qmail@stuge.se> (raw)
In-Reply-To: <a345e995a816576a4c2c39aec43716c18011475b.1291266731.git.joe@perches.com>

Joe Perches wrote:
> +++ b/drivers/net/wireless/ath/ath9k/ar9002_calib.c
..
> @@ -734,7 +734,7 @@ static bool ar9285_hw_cl_cal(struct ath_hw *ah, struct ath9k_channel *chan)
>  	if (!ath9k_hw_wait(ah, AR_PHY_AGC_CONTROL, AR_PHY_AGC_CONTROL_CAL,
>  			  0, AH_WAIT_TIMEOUT)) {
>  		ath_dbg(common, ATH_DBG_CALIBRATE,
> -			"offset calibration failed to complete in 1ms; noisy ??\n");
> +			"offset calibration failed to complete in 1ms; noisy enfironment?\n");

enfironment? :)


> +++ b/drivers/net/wireless/ath/ath9k/eeprom_4k.c
..
> @@ -1178,7 +1178,7 @@ static u16 ath9k_hw_4k_get_spur_channel(struct ath_hw *ah, u16 i, bool is2GHz)
>  	u16 spur_val = AR_NO_SPUR;
>  
>  	ath_dbg(common, ATH_DBG_ANI,
> -		"Getting spur idx %d is2Ghz. %d val %x\n",
> +		"Getting spur idx:%d is2Ghz:%d val:%x\n",
>  		i, is2GHz, ah->config.spurchans[i][is2GHz]);

Is this short for "spurious" ?


//Peter

  reply	other threads:[~2010-12-02  5:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02  5:13 [PATCH 1/2] ath: Fix ath_dbg uses missing newlines and access beyond array bound Joe Perches
2010-12-02  5:13 ` [PATCH 2/2] ath: Fix logging message typos Joe Perches
2010-12-02  5:30   ` Peter Stuge [this message]
2010-12-02  5:34     ` [ath9k-devel] " Joe Perches
2010-12-02  6:01       ` Nick Kossifidis
2010-12-02  5:35 ` [PATCH 2/2 V2] " Joe Perches
2010-12-02 19:02 ` [PATCH 1/2] ath: Fix ath_dbg uses missing newlines and access beyond array bound Luis R. Rodriguez
2010-12-03  3:12   ` [PATCH 0/4] ath: logging message conversion Joe Perches
2010-12-03  3:12     ` [PATCH 1/4] ath: Add and use ath_printk and ath_<level> Joe Perches
2010-12-07 21:38       ` John W. Linville
2010-12-03  3:12     ` [PATCH 2/4] ath: Convert ath_print(.., ATH_DBG_FATAL to ath_err Joe Perches
2010-12-03  3:12     ` [PATCH 3/4] ath: Convert ath_print to ath_dbg Joe Perches
2010-12-03  3:12     ` [PATCH 4/4] ath: Fix ath_dbg access beyond array bound Joe Perches
2010-12-07 19:05     ` [PATCH 0/4] ath: logging message conversion John W. Linville
2010-12-07 19:26       ` Luis R. Rodriguez

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=20101202053055.19479.qmail@stuge.se \
    --to=peter@stuge.se \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=ath9k-devel@venema.h4ckr.net \
    --cc=jirislaby@gmail.com \
    --cc=jmalinen@atheros.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=me@bobcopeland.com \
    --cc=mickflemm@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=senthilkumar@atheros.com \
    --cc=vasanth@atheros.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

all inboxes | Powered by JetHome®