From: Mike Snitzer <snitzer@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: kbuild test robot <lkp@intel.com>,
mika.westerberg@linux.intel.com,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
dm-devel@redhat.com, Yury Norov <ynorov@caviumnetworks.com>,
kbuild-all@01.org, linux-input@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Shaohua Li <shli@kernel.org>, Alasdair Kergon <agk@redhat.com>
Subject: Re: [PATCH v2 1/5] md: Avoid namespace collision with bitmap API
Date: Mon, 18 Jun 2018 09:36:37 -0400 [thread overview]
Message-ID: <20180618133637.GB25400@redhat.com> (raw)
In-Reply-To: <e4524ae9650c308245ecf398a0c27c6f7924be03.camel@linux.intel.com>
On Fri, Jun 15 2018 at 10:58am -0400,
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> On Fri, 2018-06-15 at 23:09 +0800, kbuild test robot wrote:
> > Hi Andy,
> >
> > I love your patch! Yet something to improve:
>
> Thanks!
>
> I fixed that locally (definitely that module wasn't compiled by
> default). Though I would wait to gather more comments before sending v3.
>
Hi,
DM is not MD. drivers/md/persistent-data/* is only used by DM.
Please rename all the drivers/md/persistent-data/ changes to use a
"dm_bitmap" prefix.
Thanks,
Mike
> > [auto build test ERROR on next-20180615]
> > [also build test ERROR on v4.17]
> > [cannot apply to md/for-next linus/master dm/for-next v4.17 v4.17-rc7
> > v4.17-rc6]
> > [if your patch is applied to the wrong git tree, please drop us a note
> > to help improve the system]
> >
> > url: https://github.com/0day-ci/linux/commits/Andy-Shevchenko/bitma
> > p-Introduce-alloc-free-helpers/20180615-214724
> > config: i386-randconfig-b0-06141412 (attached as .config)
> > compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
> > reproduce:
> > # save the attached .config to linux build tree
> > make ARCH=i386
> >
> > All errors (new ones prefixed by >>):
> >
> > > > drivers/md/persistent-data/dm-space-map-common.c:111:23: error:
> > > > 'bitmap_prepare_for_write' undeclared here (not in a function)
> >
> > .prepare_for_write = bitmap_prepare_for_write,
> > ^
> > > > drivers/md/persistent-data/dm-space-map-common.c:112:11: error:
> > > > 'bitmap_check' undeclared here (not in a function)
> >
> > .check = bitmap_check
> > ^
> > drivers/md/persistent-data/dm-space-map-common.c:72:13: warning:
> > 'md_bitmap_prepare_for_write' defined but not used [-Wunused-function]
> > static void md_bitmap_prepare_for_write(struct dm_block_validator
> > *v,
> > ^
> > drivers/md/persistent-data/dm-space-map-common.c:84:12: warning:
> > 'md_bitmap_check' defined but not used [-Wunused-function]
> > static int md_bitmap_check(struct dm_block_validator *v,
> > ^
> >
> > vim +/bitmap_prepare_for_write +111 drivers/md/persistent-data/dm-
> > space-map-common.c
> >
> > 3241b1d3 Joe Thornber 2011-10-31 108
> > 3241b1d3 Joe Thornber 2011-10-31 109 static struct
> > dm_block_validator dm_sm_bitmap_validator = {
> > 3241b1d3 Joe Thornber 2011-10-31 110 .name = "sm_bitmap",
> > 3241b1d3 Joe Thornber 2011-10-31 @111 .prepare_for_write =
> > bitmap_prepare_for_write,
> > 3241b1d3 Joe Thornber 2011-10-31 @112 .check = bitmap_check
> > 3241b1d3 Joe Thornber 2011-10-31 113 };
> > 3241b1d3 Joe Thornber 2011-10-31 114
> >
> > :::::: The code at line 111 was first introduced by commit
> > :::::: 3241b1d3e0aaafbfcd320f4d71ade629728cc4f4 dm: add persistent
> > data library
> >
> > :::::: TO: Joe Thornber <thornber@redhat.com>
> > :::::: CC: Alasdair G Kergon <agk@redhat.com>
> >
> > ---
> > 0-DAY kernel test infrastructure Open Source Technology
> > Center
> > https://lists.01.org/pipermail/kbuild-all Intel
> > Corporation
>
> --
> Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Intel Finland Oy
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2018-06-18 13:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 13:20 [PATCH v2 0/5] bitmap: Introduce alloc/free helpers Andy Shevchenko
2018-06-15 13:20 ` [PATCH v2 1/5] md: Avoid namespace collision with bitmap API Andy Shevchenko
2018-06-15 15:09 ` kbuild test robot
2018-06-15 15:09 ` kbuild test robot
2018-06-15 14:58 ` Andy Shevchenko
2018-06-18 13:36 ` Mike Snitzer [this message]
2018-06-15 15:19 ` kbuild test robot
2018-06-15 15:19 ` kbuild test robot
2018-06-15 13:20 ` [PATCH v2 2/5] bitmap: Drop unnecessary 0 check for u32 array operations Andy Shevchenko
2018-06-15 13:20 ` [PATCH v2 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free() Andy Shevchenko
2018-06-15 22:23 ` Yury Norov
2018-06-16 18:42 ` Andy Shevchenko
2018-06-15 13:20 ` [PATCH v2 4/5] Input: gpio-keys - Switch to bitmap_zalloc() Andy Shevchenko
2018-06-15 22:06 ` Yury Norov
2018-06-16 18:50 ` Andy Shevchenko
2018-06-15 13:20 ` [PATCH v2 5/5] Input: evdev " Andy Shevchenko
2018-06-15 21:42 ` Yury Norov
2018-06-16 18:45 ` Andy Shevchenko
2018-06-16 19:16 ` Joe Perches
2018-06-18 12:02 ` Andy Shevchenko
2018-06-18 15:49 ` Joe Perches
2018-06-18 19:56 ` Andy Shevchenko
2018-06-18 20:40 ` Joe Perches
2018-06-19 18:33 ` Dmitry Torokhov
2018-06-20 8:13 ` Yury Norov
2018-06-20 8:13 ` Yury Norov
2018-06-20 20:26 ` Dmitry Torokhov
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=20180618133637.GB25400@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dm-devel@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=shli@kernel.org \
--cc=ynorov@caviumnetworks.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.