From: Yury Norov <yury.norov@gmail.com>
To: linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Yury Norov <yury.norov@gmail.com>
Subject: [PATCH 0/6] bitmap: remove _reg_op()
Date: Thu, 27 Oct 2022 18:48:28 -0700 [thread overview]
Message-ID: <20221028014834.572819-1-yury.norov@gmail.com> (raw)
_reg_op() duplicates functionality of other bitmap functions.
This series removes it.
On top of this:
https://lore.kernel.org/lkml/20221027043810.350460-1-yury.norov@gmail.com/
Yury Norov (6):
bitmap: add bitmap_empty_from()
bitmap: replace _reg_op(REG_OP_ALLOC) with bitmap_set()
bitmap: replace _reg_op(REG_OP_RELEASE) with bitmap_clear()
bitmap: replace _reg_op(REG_OP_ISFREE) with bitmap_empty_from()
bitmap: fix opencoded bitmap_allocate_region()
bitmap: drop _reg_op()
include/linux/bitmap.h | 11 ++++++
lib/bitmap.c | 89 +++---------------------------------------
2 files changed, 17 insertions(+), 83 deletions(-)
--
2.34.1
next reply other threads:[~2022-10-28 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 1:48 Yury Norov [this message]
2022-10-28 1:48 ` [PATCH 1/6] bitmap: add bitmap_empty_from() Yury Norov
2022-10-28 1:48 ` [PATCH 2/6] bitmap: replace _reg_op(REG_OP_ALLOC) with bitmap_set() Yury Norov
2022-11-11 6:54 ` kernel test robot
2022-10-28 1:48 ` [PATCH 3/6] bitmap: replace _reg_op(REG_OP_RELEASE) with bitmap_clear() Yury Norov
2022-10-28 1:48 ` [PATCH 4/6] bitmap: replace _reg_op(REG_OP_ISFREE) with bitmap_empty_from() Yury Norov
2022-10-28 1:48 ` [PATCH 5/6] bitmap: fix opencoded bitmap_allocate_region() Yury Norov
2022-10-28 1:48 ` [PATCH 6/6] bitmap: drop _reg_op() Yury Norov
2022-11-03 2:09 ` [PATCH 0/6] bitmap: remove _reg_op() Yury Norov
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=20221028014834.572819-1-yury.norov@gmail.com \
--to=yury.norov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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
all inboxes | Powered by JetHome®