linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alasdair G Kergon <agk@redhat.com>, Mike Snitzer <snitzer@redhat.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>
Subject: linux-next: build failure after merge of the device-mapper tree
Date: Sun, 1 Nov 2015 21:43:57 +1100	[thread overview]
Message-ID: <20151101214357.058b19de@canb.auug.org.au> (raw)

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

             reply	other threads:[~2015-11-01 10:44 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-01 10:43 Stephen Rothwell [this message]
2015-11-01 13:44 ` linux-next: build failure after merge of the device-mapper tree Mike Snitzer
  -- strict thread matches above, loose matches on Subject: below --
2024-02-07  3:40 Stephen Rothwell
2024-02-07  3:54 ` Matthew Sakai
2024-02-07 15:47 ` Mike Snitzer
2023-09-15  0:06 Stephen Rothwell
2023-06-23  4:30 Stephen Rothwell
2023-06-23 16:47 ` Demi Marie Obenour
2021-02-11  3:36 Stephen Rothwell
2021-02-11 14:37 ` Mike Snitzer
2020-04-22  2:54 Stephen Rothwell
2018-12-06  6:21 Stephen Rothwell
2018-12-06 13:41 ` Mike Snitzer
2018-12-06 20:23   ` Stephen Rothwell
2018-05-31  4:23 Stephen Rothwell
2018-05-31  4:35 ` Jens Axboe
2018-05-31  4:38   ` Stephen Rothwell
2018-05-31 12:10   ` Mike Snitzer
2018-05-31 14:20     ` Jens Axboe
2018-05-31 14:22       ` Jens Axboe
2018-05-31 15:02         ` Jens Axboe
2018-05-31 21:42           ` Stephen Rothwell
2018-03-27  2:39 Stephen Rothwell
2018-03-27 15:39 ` Bart Van Assche
2017-06-19  2:27 Stephen Rothwell
2017-06-09  3:12 Stephen Rothwell
2017-06-09  4:28 ` Damien Le Moal
2017-06-09 11:59   ` Mike Snitzer
2016-03-04  2:59 Stephen Rothwell
2016-03-04  3:14 ` Mike Snitzer
2015-07-05 23:27 Stephen Rothwell
2015-05-22  3:27 Stephen Rothwell
2015-05-22 12:49 ` Mike Snitzer
2015-05-22 13:26   ` Mike Snitzer
2015-05-22 14:58     ` Jens Axboe
2014-01-15  3:52 Stephen Rothwell
2014-01-15  4:30 ` Mike Snitzer
2013-11-05  2:51 Stephen Rothwell
2013-11-05  3:20 ` Mike Snitzer
2013-11-05  3:32   ` Stephen Rothwell
2013-11-05 12:54     ` Mike Snitzer
2013-11-05 16:22       ` Jens Axboe
2013-11-05 22:42         ` Stephen Rothwell
2013-11-05 22:44           ` Jens Axboe
2010-08-02  1:31 Stephen Rothwell
2010-08-02  6:44 ` Milan Broz
2010-08-02 11:34 ` Alasdair G Kergon
2010-06-30  2:57 Stephen Rothwell

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=20151101214357.058b19de@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=agk@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=snitzer@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).