From: kbuild test robot <lkp@intel.com>
To: Ram Pai <linuxram@us.ibm.com>
Cc: kbuild-all@01.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, dm-devel@redhat.com,
linux-raid@vger.kernel.org, agk@redhat.com, snitzer@redhat.com,
corbet@lwn.net, shli@kernel.org, hbabu@us.ibm.com,
linuxram@us.ibm.com
Subject: Re: [PATCH v4 1/1] DM: inplace compressed DM target
Date: Tue, 14 Feb 2017 08:16:40 +0800 [thread overview]
Message-ID: <201702140843.RWFDvMkn%fengguang.wu@intel.com> (raw)
In-Reply-To: <1487018545-5061-2-git-send-email-linuxram@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2426 bytes --]
Hi Ram,
[auto build test WARNING on dm/for-next]
[also build test WARNING on v4.10-rc8 next-20170213]
[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/Ram-Pai/DM-inplace-compressed-DM-target/20170214-055727
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 4.9.0
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=m68k
All warnings (new ones prefixed by >>):
drivers/md/dm-inplace-compress.c: In function 'dm_icomp_status':
>> drivers/md/dm-inplace-compress.c:2096:3: warning: format '%ld' expects argument of type 'long int', but argument 4 has type 'long long int' [-Wformat=]
DMEMIT("%ld %ld %ld",
^
drivers/md/dm-inplace-compress.c:2096:3: warning: format '%ld' expects argument of type 'long int', but argument 5 has type 'long long int' [-Wformat=]
drivers/md/dm-inplace-compress.c:2096:3: warning: format '%ld' expects argument of type 'long int', but argument 6 has type 'long long int' [-Wformat=]
vim +2096 drivers/md/dm-inplace-compress.c
2080 req->locked_locks = 0;
2081
2082 req->cpu = raw_smp_processor_id();
2083 dm_icomp_queue_req(info, req);
2084
2085 return DM_MAPIO_SUBMITTED;
2086 }
2087
2088 static void dm_icomp_status(struct dm_target *ti, status_type_t type,
2089 unsigned int status_flags, char *result, unsigned int maxlen)
2090 {
2091 struct dm_icomp_info *info = ti->private;
2092 unsigned int sz = 0;
2093
2094 switch (type) {
2095 case STATUSTYPE_INFO:
> 2096 DMEMIT("%ld %ld %ld",
2097 atomic64_read(&info->uncompressed_write_size),
2098 atomic64_read(&info->compressed_write_size),
2099 atomic64_read(&info->meta_write_size));
2100 break;
2101 case STATUSTYPE_TABLE:
2102 if (info->write_mode == DMCP_WRITE_BACK)
2103 DMEMIT("%s %s:%d %s:%s %s:%d", info->dev->name,
2104 "writeback", info->writeback_delay,
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38918 bytes --]
next prev parent reply other threads:[~2017-02-14 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 20:42 [PATCH v4] DM: dm-inplace-compress: " Ram Pai
2017-02-13 20:42 ` [PATCH v4 1/1] DM: " Ram Pai
2017-02-14 0:16 ` kbuild test robot [this message]
2017-02-14 3:59 ` kbuild test robot
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=201702140843.RWFDvMkn%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=agk@redhat.com \
--cc=corbet@lwn.net \
--cc=dm-devel@redhat.com \
--cc=hbabu@us.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=shli@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
all inboxes | Powered by JetHome®