From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, dm <dm-devel@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
Alasdair G Kergon <agk@redhat.com>
Subject: Re: linux-next: Tree for Feb 2 (drivers/md/dm.c)
Date: Thu, 2 Feb 2017 09:58:26 -0800 [thread overview]
Message-ID: <8a8224e7-4c90-7fa7-9960-fc04fe658014@infradead.org> (raw)
In-Reply-To: <20170202182117.73e354f1@canb.auug.org.au>
On 02/01/17 23:21, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20170201:
>
on x86_64:
drivers/built-in.o: In function `dm_blk_ioctl':
dm.c:(.text+0x1a5121): undefined reference to `scsi_verify_blk_ioctl'
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_BLK_DEV_BSGLIB is not set
--
~Randy
next prev parent reply other threads:[~2017-02-02 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 7:21 linux-next: Tree for Feb 2 Stephen Rothwell
2017-02-02 17:58 ` Randy Dunlap [this message]
2017-02-02 18:29 ` linux-next: Tree for Feb 2 (drivers/md/dm.c) Mike Snitzer
2017-02-02 18:44 ` [dm-devel] " Christoph Hellwig
2017-02-02 20:19 ` Paolo Bonzini
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=8a8224e7-4c90-7fa7-9960-fc04fe658014@infradead.org \
--to=rdunlap@infradead.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).