linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@winlab.rutgers.edu>
Cc: linville@tuxdriver.com, ath5k-devel@lists.ath5k.org,
	linux-wireless@vger.kernel.org, bruno@thinktube.com,
	johannes@sipsolutions.net, mickflemm@gmail.com
Subject: Re: [PATCH 1/1] ath5k: Cleanup after API changes patch
Date: Fri, 01 Feb 2008 16:46:18 +0100	[thread overview]
Message-ID: <47A33ECA.5030005@gmail.com> (raw)
In-Reply-To: <20080201012544.GD28995@ruslug.rutgers.edu>

On 02/01/2008 02:25 AM, Luis R. Rodriguez wrote:
> Cleanup after API changes patch (checkpatch.pl stuff) and on
> ath5k_hw_rf5112_channel() make use of the new channel->band and
> existing ath5k_channel_ok() instead of re-implementing the checks
> again. This was necessary to make the code cleaner and fit
> the 80-chars wide limit so sending it within the same patch.
> 
> Finally make a note that we should eventually move cap_range stuff
> to struct wiphy.
> 
> This patch applies ontop of Nick's API changes patch.
> 
> Signed-off-by: Luis R. Rodriguez <mcgrof@winlab.rutgers.edu>
> 
> drivers/net/wireless/ath5k/ath5k.h:	Changes-licensed-under: ISC
> drivers/net/wireless/ath5k/base.c:	Changes-licensed-under: 3-Clause-BSD
> drivers/net/wireless/ath5k/initvals.c:	Changes-licensed-under: ISC
> drivers/net/wireless/ath5k/phy.c:	Changes-licensed-under: ISC
> ---
>  drivers/net/wireless/ath5k/ath5k.h    |    8 ++-
>  drivers/net/wireless/ath5k/base.c     |  126 +++++++++++++++++++--------------
>  drivers/net/wireless/ath5k/initvals.c |    6 +-
>  drivers/net/wireless/ath5k/phy.c      |   48 +++++++++----
>  4 files changed, 118 insertions(+), 70 deletions(-)
> 
[...]
> diff --git a/drivers/net/wireless/ath5k/base.c b/drivers/net/wireless/ath5k/base.c
> index 8ddac36..bd9c9a8 100644
> --- a/drivers/net/wireless/ath5k/base.c
> +++ b/drivers/net/wireless/ath5k/base.c
[...]
> @@ -889,13 +900,15 @@ ath5k_copy_channels(struct ath5k_hw *ah,
>  		/* Write channel info and increment counter */
>  		channels[count].center_freq = freq;
>  
> -		if((mode == AR5K_MODE_11A) ||
> -		(mode == AR5K_MODE_11G)){
> -			channels[count].hw_value = chfreq|CHANNEL_OFDM;
> -		} else if((mode == AR5K_MODE_11A_TURBO) ||
> -		(mode == AR5K_MODE_11G_TURBO)){
> -			channels[count].hw_value = chfreq|CHANNEL_OFDM|CHANNEL_TURBO;
> -		}if(mode == AR5K_MODE_11B) {
> +		if ((mode == AR5K_MODE_11A) ||
> +			(mode == AR5K_MODE_11G)) {
> +			channels[count].hw_value =
> +				chfreq | CHANNEL_OFDM;
> +		} else if ((mode == AR5K_MODE_11A_TURBO) ||
> +			(mode == AR5K_MODE_11G_TURBO)) {
> +			channels[count].hw_value =
> +				chfreq | CHANNEL_OFDM|CHANNEL_TURBO;
> +		} if (mode == AR5K_MODE_11B) {

'else' or '\n' before the if, please

>  			channels[count].hw_value = CHANNEL_B;
>  		}
>  


  parent reply	other threads:[~2008-02-01 15:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  1:25 [PATCH 1/1] ath5k: Cleanup after API changes patch Luis R. Rodriguez
2008-02-01 12:38 ` Johannes Berg
2008-02-01 12:41   ` Luis R. Rodriguez
2008-02-01 12:46     ` Johannes Berg
2008-02-01 12:52       ` [ath5k-devel] " Luis R. Rodriguez
2008-02-01 15:20         ` Johannes Berg
2008-02-01 21:28           ` Luis R. Rodriguez
2008-02-01 18:47         ` Nick Kossifidis
2008-02-01 21:45           ` Luis R. Rodriguez
2008-02-02 22:19             ` Luis R. Rodriguez
2008-02-02 23:07               ` Nick Kossifidis
2008-02-02 23:24                 ` Luis R. Rodriguez
2008-02-01 15:46 ` Jiri Slaby [this message]
2008-02-02 21:35   ` Luis R. Rodriguez
2008-02-02 21:39     ` Luis R. Rodriguez
2008-02-02 22:20       ` Jiri Slaby
2008-02-02 22:28         ` Luis R. Rodriguez
2008-02-02 23:40           ` 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=47A33ECA.5030005@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=bruno@thinktube.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@winlab.rutgers.edu \
    --cc=mickflemm@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;
as well as URLs for NNTP newsgroup(s).