From: Joe Perches <joe@perches.com>
To: "Wang, Yalin" <Yalin.Wang@sonymobile.com>
Cc: "'chunkeey@googlemail.com'" <chunkeey@googlemail.com>,
"'linville@tuxdriver.com'" <linville@tuxdriver.com>,
"'linux-wireless@vger.kernel.org'"
<linux-wireless@vger.kernel.org>,
"'netdev@vger.kernel.org'" <netdev@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] carl9170: Convert byte_rev_table uses to bitrev8
Date: Thu, 13 Nov 2014 21:32:44 -0800 [thread overview]
Message-ID: <1415943164.5912.4.camel@perches.com> (raw)
In-Reply-To: <35FD53F367049845BC99AC72306C23D103E010D1829D@CNBJMBX05.corpusers.net>
On Fri, 2014-11-14 at 13:16 +0800, Wang, Yalin wrote:
> Use the inline function instead of directly indexing the array.
>
> This allows some architectures with hardware instructions for bit
> reversals to eliminate the array.
This one is already in -next
commit 7a1283d8f5298437a454ec477384dcd9f9f88bac
Author: Joe Perches <joe@perches.com>
Date: Tue Oct 28 14:18:58 2014 -0700
carl9170: Convert byte_rev_table uses to bitrev8
Use the inline function instead of directly indexing the array.
This allows some architectures with hardware instructions
for bit reversals to eliminate the array.
Signed-off-by: Joe Perches <joe@perches.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
next prev parent reply other threads:[~2014-11-14 5:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 5:16 [PATCH] carl9170: Convert byte_rev_table uses to bitrev8 Wang, Yalin
2014-11-14 5:32 ` Joe Perches [this message]
2014-11-14 5:37 ` Wang, Yalin
[not found] <35FD53F367049845BC99AC72306C23D103E010D18254@CNBJMBX05.corpusers.net>
[not found] ` <35FD53F367049845BC99AC72306C23D103E010D18257@CNBJMBX05.corpusers.net>
[not found] ` <1414392371.8884.2.camel@perches.com>
2014-10-28 21:18 ` Joe Perches
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=1415943164.5912.4.camel@perches.com \
--to=joe@perches.com \
--cc=Yalin.Wang@sonymobile.com \
--cc=chunkeey@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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).