From: Wei Yang <richard.weiyang@linux.alibaba.com>
To: akpm@linux-foundation.org, christian.brauner@ubuntu.com,
andriy.shevchenko@linux.intel.com
Cc: linux-kernel@vger.kernel.org,
Wei Yang <richard.weiyang@linux.alibaba.com>
Subject: [RESEND Patch 0/2] trivial cleanup for get_count_order[_long]
Date: Fri, 7 Aug 2020 16:58:35 +0800 [thread overview]
Message-ID: <20200807085837.11697-1-richard.weiyang@linux.alibaba.com> (raw)
The following two patches cleanup get_count_order[_long] a little.
The lib/test_bitops pass with these two patches.
Wei Yang (2):
bitops: simplify get_count_order_long()
bitops: use the same mechanism for get_count_order[_long]
include/linux/bitops.h | 13 ++++---------
1 file changed, 4 insertions(+), 9 deletions(-)
--
2.20.1 (Apple Git-117)
next reply other threads:[~2020-08-07 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 8:58 Wei Yang [this message]
2020-08-07 8:58 ` [RESEND Patch 1/2] bitops: simplify get_count_order_long() Wei Yang
2020-08-07 8:58 ` [RESEND Patch 2/2] bitops: use the same mechanism for get_count_order[_long] Wei Yang
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=20200807085837.11697-1-richard.weiyang@linux.alibaba.com \
--to=richard.weiyang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=christian.brauner@ubuntu.com \
--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;
as well as URLs for NNTP newsgroup(s).