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

From	Christoph Hellwig <hch@lst.de>
Newsgroups	linux.kernel
Subject	Re: linux-next: build failure after merge of the block tree
Date	2017-01-30 07:50 +0100
Message-ID	<t5dWO-EH-3@gated-at.bofh.it> (permalink)
References	<t59gt-6em-1@gated-at.bofh.it> <t59q9-6hP-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Sun, Jan 29, 2017 at 06:53:42PM -0700, Jens Axboe wrote:
> Huh, I wonder how that snuck past my allmodconfig builds, that looks
> like a clear failure.

I also did tons of test builds and never saw it, not sure why
the NVMe-SCSI code still someone how an implicit include of scsi_cmnd.h.

But in the end it should not be using the defintion anyway, and I sent
a patch on Saturday so that it doesn't:

	[PATCH 1/5] nvme/scsi: don't rely on BLK_MAX_CDB

might make sense to expedite that.

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

Thread

linux-next: build failure after merge of the block tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-01-30 02:50 +0100
  Re: linux-next: build failure after merge of the block tree Jens Axboe <axboe@kernel.dk> - 2017-01-30 03:00 +0100
    Re: linux-next: build failure after merge of the block tree Jens Axboe <axboe@kernel.dk> - 2017-01-30 04:10 +0100
    Re: linux-next: build failure after merge of the block tree Christoph Hellwig <hch@lst.de> - 2017-01-30 07:50 +0100

csiph-web