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

Groups > linux.kernel > #1260121 > unrolled thread

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

Back to article view | Back to linux.kernel

Contents

  linux-next: build failure after merge of the device-mapper tree Stephen Rothwell <sfr@canb.auug.org.au> - 2015-11-01 11:50 +0100
    Re: linux-next: build failure after merge of the device-mapper tree Mike Snitzer <snitzer@redhat.com> - 2015-11-01 14:50 +0100

#1260121 — linux-next: build failure after merge of the device-mapper tree

Hi all,

After merging the device-mapper tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

drivers/md/dm-mpath.c: In function 'multipath_prepare_ioctl':
drivers/md/dm-mpath.c:1570:41: error: 'cmd' undeclared (first use in this function)
   int err = scsi_verify_blk_ioctl(NULL, cmd);
                                         ^

Caused by commit

  21a2807bc3ff ("dm: refactor ioctl handling")

I have used the device-mapper tree from next-20151022 for today.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1260160

On Sun, Nov 01 2015 at  5:43am -0500,
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> After merging the device-mapper tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> drivers/md/dm-mpath.c: In function 'multipath_prepare_ioctl':
> drivers/md/dm-mpath.c:1570:41: error: 'cmd' undeclared (first use in this function)
>    int err = scsi_verify_blk_ioctl(NULL, cmd);
>                                          ^
> 
> Caused by commit
> 
>   21a2807bc3ff ("dm: refactor ioctl handling")
> 
> I have used the device-mapper tree from next-20151022 for today.

There was a ~3 hour window yesterday where this was broken.  I resolved
it almost 12 hours prior to you having sent this mail.

Do you batch update the trees you pull into linux-next at some point
much earlier in the day?

If/when you do hit a tree that is clearly broken at the time you
pulled: do you attempt to re-pull to get the latest _before_ reverting
to some prior linux-next version of the tree in question?

Anyway, sorry the device-mapper tree was broken for a small window of
time yesterday -- but of course linux-next pulled during that window ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web