Date: Sun, 1 Nov 2015 08:44:11 -0500
From: Mike Snitzer <snitzer@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alasdair G Kergon <agk@redhat.com>, linux-next@vger.kernel.org,
        linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: build failure after merge of the device-mapper tree
Message-ID: <20151101134411.GA16936@redhat.com>
References: <20151101214357.058b19de@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20151101214357.058b19de@canb.auug.org.au>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1407
Lines: 36

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/