From: kernel test robot <lkp@intel.com>
To: Yang Li <yang.lee@linux.alibaba.com>, agk@redhat.com
Cc: kbuild-all@lists.01.org, snitzer@redhat.com, dm-devel@redhat.com,
linux-kernel@vger.kernel.org,
Yang Li <yang.lee@linux.alibaba.com>
Subject: Re: [PATCH] dm: remove unneeded variable 'sz'
Date: Wed, 10 Mar 2021 01:24:38 +0800 [thread overview]
Message-ID: <202103100144.QZzf2C63-lkp@intel.com> (raw)
In-Reply-To: <1615282320-28246-1-git-send-email-yang.lee@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 2517 bytes --]
Hi Yang,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on dm/for-next]
[also build test ERROR on v5.12-rc2 next-20210309]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Yang-Li/dm-remove-unneeded-variable-sz/20210309-173431
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
config: x86_64-rhel-7.6-kselftests (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/a0feb390ae71f527ea5582a23afa1889bba31eab
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Yang-Li/dm-remove-unneeded-variable-sz/20210309-173431
git checkout a0feb390ae71f527ea5582a23afa1889bba31eab
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from drivers/md/dm.h:14,
from drivers/md/dm-ps-service-time.c:11:
drivers/md/dm-ps-service-time.c: In function 'st_status':
>> include/linux/device-mapper.h:588:22: error: 'sz' undeclared (first use in this function); did you mean 's8'?
588 | #define DMEMIT(x...) sz += ((sz >= maxlen) ? \
| ^~
drivers/md/dm-ps-service-time.c:88:3: note: in expansion of macro 'DMEMIT'
88 | DMEMIT("0 ");
| ^~~~~~
include/linux/device-mapper.h:588:22: note: each undeclared identifier is reported only once for each function it appears in
588 | #define DMEMIT(x...) sz += ((sz >= maxlen) ? \
| ^~
drivers/md/dm-ps-service-time.c:88:3: note: in expansion of macro 'DMEMIT'
88 | DMEMIT("0 ");
| ^~~~~~
vim +588 include/linux/device-mapper.h
0da336e5fab75c Alasdair G Kergon 2008-04-24 587
0da336e5fab75c Alasdair G Kergon 2008-04-24 @588 #define DMEMIT(x...) sz += ((sz >= maxlen) ? \
0da336e5fab75c Alasdair G Kergon 2008-04-24 589 0 : scnprintf(result + sz, maxlen - sz, x))
0da336e5fab75c Alasdair G Kergon 2008-04-24 590
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 50496 bytes --]
next prev parent reply other threads:[~2021-03-09 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 9:32 [PATCH] dm: remove unneeded variable 'sz' Yang Li
2021-03-09 13:38 ` kernel test robot
2021-03-09 17:24 ` kernel test robot [this message]
2021-03-09 20:14 ` Mike Snitzer
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=202103100144.QZzf2C63-lkp@intel.com \
--to=lkp@intel.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@redhat.com \
--cc=yang.lee@linux.alibaba.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