Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1662358

Re: linux-next: build failure after merge of the device-mapper tree

From Mike Snitzer <snitzer@redhat.com>
Newsgroups linux.kernel
Subject Re: linux-next: build failure after merge of the device-mapper tree
Date 2017-06-09 14:00 +0200
Message-ID <tQqK5-13J-15@gated-at.bofh.it> (permalink)
References <tQiCS-4Bd-7@gated-at.bofh.it> <tQjIC-5hD-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Fri, Jun 09 2017 at 12:28am -0400,
Damien Le Moal <damien.lemoal@wdc.com> wrote:

> Stephen,
> 
> On 6/9/17 12:12, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the device-mapper tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > drivers/md/dm-zoned-target.c:947:2: error: unknown field 'suspend' specified in initializer
> >   .suspend  = dmz_suspend,
> >   ^
> > drivers/md/dm-zoned-target.c:947:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
> >   .suspend  = dmz_suspend,
> >               ^
> > 
> > Caused by commit
> > 
> >   02da2e15e81f ("dm zoned: drive-managed zoned block device target")
> > 
> > I have used the device-mapper tree from next-20170608 for today.
> 
> My apologies for that. My mistake.
> I just posted a patch to dm-devel to fix this.
> Everything should come in order after Mike's review.

I'm to blame for the above issue.  I've now fixed it up.

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

linux-next: build failure after merge of the device-mapper tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-09 05:20 +0200
  Re: linux-next: build failure after merge of the device-mapper tree Damien Le Moal <damien.lemoal@wdc.com> - 2017-06-09 06:30 +0200
    Re: linux-next: build failure after merge of the device-mapper tree Mike Snitzer <snitzer@redhat.com> - 2017-06-09 14:00 +0200

csiph-web