From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: bitmap API consistency
Date: Wed, 24 May 2017 15:11:21 +0300 [thread overview]
Message-ID: <1495627881.6967.99.camel@linux.intel.com> (raw)
Hi!
Surprisingly discovered today that bitmap API is not consistent in some
cases (at least one I found recently).
bitmap_fill() sets area of bits in a bitmap.
bitmap_zero() clears them.
However, if _fill() does something sane, _zero() clears _all_ bits up to
word size (long).
I think it should be fixed to be consistent with _fill() variant.
Thoughts?
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next reply other threads:[~2017-05-24 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 12:11 Andy Shevchenko [this message]
2017-05-24 12:38 ` bitmap API consistency Rasmus Villemoes
2017-05-24 12:43 ` Andy Shevchenko
2017-12-19 17:32 ` Andy Shevchenko
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=1495627881.6967.99.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=schwidefsky@de.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.