public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michalis Pappas <mpappas@fastmail.fm>
To: Ben Chan <benchan@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: gdm72xx: move T_CAPABILITY bit definitions to hci.h
Date: Tue, 01 Jul 2014 17:25:07 +0100	[thread overview]
Message-ID: <53B2E0E3.1080007@fastmail.fm> (raw)
In-Reply-To: <CAC5Y2nNhQvDve4SiV7Eat9t_82S3S26sU+p4R=vGQ2hk4tdAMg@mail.gmail.com>

On 07/01/2014 04:37 PM, Ben Chan wrote:
> On Tue, Jul 1, 2014 at 6:00 AM, Michalis Pappas <mpappas@fastmail.fm> wrote:
>> Signed-off-by: Michalis Pappas <mpappas@fastmail.fm>
>> ---
>>  drivers/staging/gdm72xx/gdm_wimax.c | 10 +++-------
>>  drivers/staging/gdm72xx/hci.h       |  6 ++++++
>>  2 files changed, 9 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/staging/gdm72xx/gdm_wimax.c b/drivers/staging/gdm72xx/gdm_wimax.c
>> index 63a760b..1fc64a9 100644
>> --- a/drivers/staging/gdm72xx/gdm_wimax.c
>> +++ b/drivers/staging/gdm72xx/gdm_wimax.c
>> @@ -600,10 +600,6 @@ static void gdm_wimax_prepare_device(struct net_device *dev)
>>         u16 len = 0;
>>         u32 val = 0;
>>
>> -       #define BIT_MULTI_CS    0
>> -       #define BIT_WIMAX               1
>> -       #define BIT_QOS                 2
>> -       #define BIT_AGGREGATION 3
>>
>>         /* GetInformation mac address */
>>         len = 0;
>> @@ -612,12 +608,12 @@ static void gdm_wimax_prepare_device(struct net_device *dev)
>>         hci->length = H2B(len);
>>         gdm_wimax_send(nic, hci, HCI_HEADER_SIZE+len);
>>
>> -       val = (1<<BIT_WIMAX) | (1<<BIT_MULTI_CS);
>> +       val = (1 << T_CAPABILITY_BIT_WIMAX) | (1 << T_CAPABILITY_BIT_MULTI_CS);
>>         #if defined(CONFIG_WIMAX_GDM72XX_QOS)
>> -       val |= (1<<BIT_QOS);
>> +       val |= (1 << T_CAPABILITY_BIT_QOS);
>>         #endif
>>         #if defined(CONFIG_WIMAX_GDM72XX_WIMAX2)
>> -       val |= (1<<BIT_AGGREGATION);
>> +       val |= (1 << T_CAPABILITY_BIT_AGGREGATION);
>>         #endif
> 
> [Ben] We can simply the code by defining these constants as bitmasks
> instead, e.g.
> 
> T_CAPABILITY_MULTI_CS  (1 << 0)
> T_CAPABILITY_WIMAX  (1 << 1)
> T_CAPABILITY_QOS  (1 << 2)
> T_CAPABILITY_AGGREGATION  (1 << 3)
> 

Agreed, I'll submit a new patch.


  reply	other threads:[~2014-07-01 16:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 13:00 [PATCH] staging: gdm72xx: remove unused code Michalis Pappas
2014-07-01 13:00 ` [PATCH] staging: gdm72xx: conditionally compile debug code Michalis Pappas
     [not found]   ` <CAC5Y2nPGyByqLEM1Go6Pxpb6MhiJy2Fvu=eEz6ak24gMhayk=A@mail.gmail.com>
2014-07-01 16:40     ` Michalis Pappas
     [not found]       ` <CAC5Y2nOvJ2=u7-T53kHd50AfQ7Mo_U4qvD_=si9=NSr_q0w3NA@mail.gmail.com>
2014-07-03 17:27         ` Michalis Pappas
2014-07-09 18:51   ` Greg KH
2014-07-09 19:52     ` Michalis Pappas
2014-07-09 20:24       ` Greg KH
2014-07-16 20:40     ` Michalis Pappas
2014-07-16 20:50       ` Greg KH
2014-07-16 22:03         ` Michalis Pappas
2014-07-16 22:10           ` Greg KH
2014-07-16 22:46             ` Joe Perches
2014-07-16 22:57               ` Greg KH
2014-07-17  0:19                 ` Joe Perches
2014-07-01 13:00 ` [PATCH] staging: gdm72xx: move T_CAPABILITY bit definitions to hci.h Michalis Pappas
2014-07-01 15:37   ` Ben Chan
2014-07-01 16:25     ` Michalis Pappas [this message]
2014-07-02 10:18   ` [PATCH V2] staging: gdm72xx: move T_CAPABILITY " Michalis Pappas
2014-07-09 10:26     ` Dan Carpenter
2014-07-09 18:24       ` Michalis Pappas
2014-07-09 18:31         ` [PATCH v3] " Michalis Pappas
2014-07-09 18:57           ` Greg KH
2014-07-09 19:21             ` [PATCH v4] " Michalis Pappas

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=53B2E0E3.1080007@fastmail.fm \
    --to=mpappas@fastmail.fm \
    --cc=benchan@chromium.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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