From: kbuild test robot <lkp@intel.com>
To: Toshi Kani <toshi.kani@hpe.com>
Cc: kbuild-all@01.org, snitzer@redhat.com, agk@redhat.com,
dan.j.williams@intel.com, linux-nvdimm@ml01.01.org,
dm-devel@redhat.com, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org, Toshi Kani <toshi.kani@hpe.com>
Subject: Re: [PATCH 2/2] dm snap: add fake origin_direct_access
Date: Wed, 29 Jun 2016 04:27:01 +0800 [thread overview]
Message-ID: <201606290450.w91c6wVU%fengguang.wu@intel.com> (raw)
In-Reply-To: <1467142636-21094-3-git-send-email-toshi.kani@hpe.com>
[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]
Hi,
[auto build test WARNING on dm/for-next]
[also build test WARNING on v4.7-rc5 next-20160628]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Toshi-Kani/Support-DAX-for-device-mapper-dm-linear-devices/20160629-034110
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
config: x86_64-lkp (attached as .config)
compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
drivers/md/dm-snap.c:2370:2: error: unknown field 'direct_access' specified in initializer
.direct_access = origin_direct_access,
^
>> drivers/md/dm-snap.c:2370:2: warning: initialization from incompatible pointer type
drivers/md/dm-snap.c:2370:2: warning: (near initialization for 'origin_target.io_hints')
vim +2370 drivers/md/dm-snap.c
2354 struct dm_origin *o = ti->private;
2355
2356 return fn(ti, o->dev, 0, ti->len, data);
2357 }
2358
2359 static struct target_type origin_target = {
2360 .name = "snapshot-origin",
2361 .version = {1, 9, 0},
2362 .module = THIS_MODULE,
2363 .ctr = origin_ctr,
2364 .dtr = origin_dtr,
2365 .map = origin_map,
2366 .resume = origin_resume,
2367 .postsuspend = origin_postsuspend,
2368 .status = origin_status,
2369 .iterate_devices = origin_iterate_devices,
> 2370 .direct_access = origin_direct_access,
2371 };
2372
2373 static struct target_type snapshot_target = {
2374 .name = "snapshot",
2375 .version = {1, 15, 0},
2376 .module = THIS_MODULE,
2377 .ctr = snapshot_ctr,
2378 .dtr = snapshot_dtr,
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 23378 bytes --]
next prev parent reply other threads:[~2016-06-28 20:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 19:37 [PATCH 0/2] Support DAX for device-mapper dm-linear devices Toshi Kani
2016-06-28 19:37 ` [PATCH 1/2] dm: update table type check for dax Toshi Kani
2016-06-28 20:07 ` Mike Snitzer
2016-06-28 20:23 ` Kani, Toshimitsu
2016-06-29 0:40 ` Mike Snitzer
2016-06-29 15:19 ` Kani, Toshimitsu
2016-06-28 20:33 ` kbuild test robot
2016-06-28 19:37 ` [PATCH 2/2] dm snap: add fake origin_direct_access Toshi Kani
2016-06-28 20:27 ` kbuild test robot [this message]
2016-06-28 19:43 ` [PATCH 0/2] fix dm-snap for dax Kani, Toshimitsu
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=201606290450.w91c6wVU%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=agk@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=linux-raid@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=toshi.kani@hpe.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
all inboxes | Powered by JetHome®