On Fri, Jun 24 2016 at 3:58pm -0400,
kbuild test robot <lkp(a)intel.com> wrote:
>
> Hi,
>
> [auto build test WARNING on dm/for-next]
> [also build test WARNING on v4.7-rc4 next-20160624]
> [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/Toshi-Kani/dm-stripe-add-
> DAX-support/20160625-022600
>
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linu
> x-dm.git for-next
> config: m68k-sun3_defconfig (attached as .config)
> compiler: m68k-linux-gcc (GCC) 4.9.0
> reproduce:
> wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.gi
> t/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=m68k
>
> All warnings (new ones prefixed by >>):
>
> drivers/md/dm-stripe.c:452:2: error: unknown field 'direct_access'
> specified in initializer
> .direct_access = stripe_direct_access,
> ^
> drivers/md/dm-stripe.c:452:2: warning: missing braces around
> initializer [-Wmissing-braces]
> drivers/md/dm-stripe.c:452:2: warning: (near initialization for
> 'stripe_target.list') [-Wmissing-braces]
> >
> > >
> > > drivers/md/dm-stripe.c:452:2: warning: initialization from
> > > incompatible pointer type
> drivers/md/dm-stripe.c:452:2: warning: (near initialization for
> 'stripe_target.list.next')
FYI, overzealous kbuild robot build failure here.. I haven't staged the
prereq DM core changes yet because I'm waiting for Jens to take the 2
block changes those depend on.
This patch applies on top of wip. Could this be because 'for-next' does not
have the previous dm/dm-linear series?
Thanks,
-Toshi