From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: improve vdev map handling.
Date: Fri, 16 May 2014 17:06:05 +0300 [thread overview]
Message-ID: <87bnux4y42.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <53761A35.2000308@candelatech.com> (Ben Greear's message of "Fri, 16 May 2014 07:01:25 -0700")
Ben Greear <greearb@candelatech.com> writes:
> On 05/16/2014 06:37 AM, Kalle Valo wrote:
>
>>> - ar->free_vdev_map &= ~BIT(arvif->vdev_id);
>>> + ar->free_vdev_map &= ~(1 << arvif->vdev_id);
>>
>> Why remove the BIT()? Not that it matters much, I just think it's easier
>> to read when BIT() macro is used. Would be good to convert all cases to
>> use BIT anyway, but that's for a separate patch.
>
> BIT doesn't work on 64-bit numbers (ie, if vdev_id > 31)
Oh, I didn't know that. Too bad, but then removing it makes sense.
> and it takes a long time to figure out exactly what it does (try
> grepping for BIT). Open-coding means much easier to fully understand
> the code.
All Linux engineers should know what BIT() does. If not, they should
learn that ;)
>>> - ar->free_vdev_map |= 1 << (arvif->vdev_id);
>>> + ar->free_vdev_map |= (1 << arvif->vdev_id);
>>
>> Do we need the parenthesis?
>
> No, though I like them visually. It's at least more useful than
> the previous placement.
>
> I can respin the patch w/out them and with the == 0 and such.
Thanks.
--
Kalle Valo
next prev parent reply other threads:[~2014-05-16 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 18:22 [PATCH] ath10k: improve vdev map handling greearb
2014-05-16 13:18 ` Kalle Valo
2014-05-16 13:26 ` Ben Greear
2014-05-16 13:37 ` Kalle Valo
2014-05-16 14:01 ` Ben Greear
2014-05-16 14:06 ` Kalle Valo [this message]
2014-05-16 14:11 ` Ben Greear
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=87bnux4y42.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).