From: kbuild test robot <lkp@intel.com>
To: Qiang Su <suqiang4@huawei.com>
Cc: kbuild-all@lists.01.org, gregkh@linuxfoundation.org,
suqiang4@huawei.com, linux-kernel@vger.kernel.org,
leeyou.li@huawei.com, nixiaoming@huawei.com
Subject: Re: [PATCH] UIO: make MAX_UIO_MAPS configurable by menuconfig
Date: Fri, 6 Mar 2020 23:04:44 +0800 [thread overview]
Message-ID: <202003062336.mR4V1rTp%lkp@intel.com> (raw)
In-Reply-To: <20200306071122.71838-1-suqiang4@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]
Hi Qiang,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on char-misc/char-misc-testing]
[also build test ERROR on v5.6-rc4 next-20200306]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Qiang-Su/UIO-make-MAX_UIO_MAPS-configurable-by-menuconfig/20200306-192239
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git 1f836f5b10f2524d33efde47d2b694b861ecf319
config: x86_64-randconfig-s0-20200306 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.2-10+deb8u1) 4.9.2
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from drivers/uio/uio.c:26:0:
>> include/linux/uio_driver.h:47:22: error: 'CONFIG_MAX_UIO_MAPS' undeclared here (not in a function)
#define MAX_UIO_MAPS CONFIG_MAX_UIO_MAPS
^
include/linux/uio_driver.h:102:22: note: in expansion of macro 'MAX_UIO_MAPS'
struct uio_mem mem[MAX_UIO_MAPS];
^
vim +/CONFIG_MAX_UIO_MAPS +47 include/linux/uio_driver.h
46
> 47 #define MAX_UIO_MAPS CONFIG_MAX_UIO_MAPS
48
---
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: 34592 bytes --]
prev parent reply other threads:[~2020-03-06 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 7:11 Qiang Su
2020-03-06 14:55 ` kbuild test robot
2020-03-06 15:04 ` kbuild test robot [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=202003062336.mR4V1rTp%lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=leeyou.li@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nixiaoming@huawei.com \
--cc=suqiang4@huawei.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®