From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Shaohua Li <shli@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
arnd@arndb.de, Andrew Morton <akpm@linux-foundation.org>
Cc: linux-raid <linux-raid@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: bitmap namespace conflict
Date: Thu, 14 Jun 2018 17:46:36 +0300 [thread overview]
Message-ID: <ad0415db268750c033499e2b3bd079ca2c9f099d.camel@linux.intel.com> (raw)
Hi!
There is a potential name space collision with bitmap API vs. MD bitmaps
(whatever it is).
Since I'm about to submit some extension to bitmap API, I would like as
a preparatory patch to rename all bitmap_* in drivers/md to md_bitmap_*
to avoid real conflict with my patch series [1], i.e. bitmap_free().
Opinions?
Better proposals?
[1]: https://patchwork.kernel.org/patch/10442771/
Almost RFC version
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
reply other threads:[~2018-06-14 14:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ad0415db268750c033499e2b3bd079ca2c9f099d.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@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).