From: Mike Snitzer <snitzer@redhat.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: dm-devel@redhat.com, kbuild-all@01.org
Subject: Re: [dm:for-next 1/4] drivers/md/dm.c:1757:36: error: passing argument 2 of 'dm_mq_init_request_queue' from incompatible pointer type
Date: Fri, 10 Jun 2016 15:18:03 -0400 [thread overview]
Message-ID: <20160610191803.GA30231@redhat.com> (raw)
In-Reply-To: <201606110159.BUvhrj8S%fengguang.wu@intel.com>
On Fri, Jun 10 2016 at 2:00pm -0400,
kbuild test robot <fengguang.wu@intel.com> wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
> head: b18ef3eb063790f62f2630015a116cb495cb143f
> commit: 3fa1ee95f14c676ef9d8f53516f31f1bdcb194f1 [1/4] dm: move request-based code out to dm-rq.[hc]
> config: i386-defconfig (attached as .config)
> compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
> reproduce:
> git checkout 3fa1ee95f14c676ef9d8f53516f31f1bdcb194f1
> # save the attached .config to linux build tree
> make ARCH=i386
>
> Note: the dm/for-next HEAD b18ef3eb063790f62f2630015a116cb495cb143f builds fine.
> It only hurts bisectibility.
>
> All errors (new ones prefixed by >>):
>
> drivers/md/dm.c: In function 'dm_setup_md_queue':
> >> drivers/md/dm.c:1757:36: error: passing argument 2 of 'dm_mq_init_request_queue' from incompatible pointer type [-Werror=incompatible-pointer-types]
> r = dm_mq_init_request_queue(md, t);
> ^
> In file included from drivers/md/dm.c:9:0:
> drivers/md/dm-rq.h:52:5: note: expected 'struct dm_target *' but argument is of type 'struct dm_table *'
> int dm_mq_init_request_queue(struct mapped_device *md, struct dm_target *immutable_tgt);
> ^~~~~~~~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
>
> vim +/dm_mq_init_request_queue +1757 drivers/md/dm.c
>
> 1751 if (r) {
> 1752 DMERR("Cannot initialize queue for request-based mapped device");
> 1753 return r;
> 1754 }
> 1755 break;
> 1756 case DM_TYPE_MQ_REQUEST_BASED:
> > 1757 r = dm_mq_init_request_queue(md, t);
> 1758 if (r) {
> 1759 DMERR("Cannot initialize queue for request-based dm-mq mapped device");
> 1760 return r;
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
I fixed this up, sorry for the noise.
prev parent reply other threads:[~2016-06-10 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 18:00 [dm:for-next 1/4] drivers/md/dm.c:1757:36: error: passing argument 2 of 'dm_mq_init_request_queue' from incompatible pointer type kbuild test robot
2016-06-10 19:18 ` Mike Snitzer [this message]
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=20160610191803.GA30231@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.