All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@winlab.rutgers.edu>
Cc: ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
	linville@tuxdriver.com, bruno@thinktube.com,
	johannes@sipsolutions.net
Subject: Re: [ath5k-devel] [PATCH 1/1] ath5k: Cleanup after API changes patch
Date: Sat, 02 Feb 2008 23:20:53 +0100	[thread overview]
Message-ID: <47A4ECC5.6070503@gmail.com> (raw)
In-Reply-To: <43e72e890802021339x5b2a44eayad71e796ba48451b@mail.gmail.com>

On 02/02/2008 10:39 PM, Luis R. Rodriguez wrote:
> On Feb 2, 2008 4:35 PM, Luis R. Rodriguez <mcgrof@winlab.rutgers.edu> wrote:
>> On Feb 1, 2008 10:46 AM, Jiri Slaby <jirislaby@gmail.com> wrote:
>>> On 02/01/2008 02:25 AM, Luis R. Rodriguez wrote:
>>>> @@ -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
>> Good catch, that should have been an "else if" there. Will repost all
>> pending patches in a series addressing all posted comments.
> 
> Going to move this to a switch, its much more legible.

There was switch IIRC, I think either sparse or -W don't like it too much (enum 
<-> int)? Please could you check? (-W doesn't bother us.)

  reply	other threads:[~2008-02-02 22:20 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
2008-02-02 21:35   ` [ath5k-devel] " Luis R. Rodriguez
2008-02-02 21:39     ` Luis R. Rodriguez
2008-02-02 22:20       ` Jiri Slaby [this message]
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=47A4ECC5.6070503@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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.