From: kernel test robot <lkp@intel.com>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>,
linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, corbet@lwn.net,
linus.walleij@linaro.org, bgolaszewski@baylibre.com,
info@metux.net, mst@redhat.com, jasowang@redhat.com,
linux-doc@vger.kernel.org, linux-gpio@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v3] drivers: gpio: add virtio-gpio guest driver
Date: Tue, 8 Dec 2020 06:13:57 +0800 [thread overview]
Message-ID: <202012080644.2LjqW7Sc-lkp@intel.com> (raw)
In-Reply-To: <20201207204838.21406-1-info@metux.net>
[-- Attachment #1: Type: text/plain, Size: 4374 bytes --]
Hi "Enrico,
I love your patch! Yet something to improve:
[auto build test ERROR on gpio/for-next]
[also build test ERROR on linux/master linus/master v5.10-rc7 next-20201207]
[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/Enrico-Weigelt-metux-IT-consult/drivers-gpio-add-virtio-gpio-guest-driver/20201208-045646
base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git for-next
config: h8300-randconfig-r032-20201207 (attached as .config)
compiler: h8300-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/fff1ac3789d850604f11c95b185116bea68e26a9
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Enrico-Weigelt-metux-IT-consult/drivers-gpio-add-virtio-gpio-guest-driver/20201208-045646
git checkout fff1ac3789d850604f11c95b185116bea68e26a9
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300
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 >>):
>> drivers/i2c/Kconfig:8:error: recursive dependency detected!
drivers/i2c/Kconfig:8: symbol I2C is selected by FB_DDC
drivers/video/fbdev/Kconfig:63: symbol FB_DDC depends on FB
drivers/video/fbdev/Kconfig:12: symbol FB is selected by DRM_KMS_FB_HELPER
drivers/gpu/drm/Kconfig:80: symbol DRM_KMS_FB_HELPER depends on DRM_KMS_HELPER
drivers/gpu/drm/Kconfig:74: symbol DRM_KMS_HELPER is selected by DRM_VIRTIO_GPU
drivers/gpu/drm/virtio/Kconfig:2: symbol DRM_VIRTIO_GPU depends on VIRTIO
drivers/virtio/Kconfig:2: symbol VIRTIO is selected by GPIO_VIRTIO
drivers/gpio/Kconfig:1628: symbol GPIO_VIRTIO depends on GPIOLIB
drivers/gpio/Kconfig:14: symbol GPIOLIB is selected by I2C_MUX_LTC4306
drivers/i2c/muxes/Kconfig:47: symbol I2C_MUX_LTC4306 depends on I2C
For a resolution refer to Documentation/kbuild/kconfig-language.rst
subsection "Kconfig recursive dependency limitations"
vim +8 drivers/i2c/Kconfig
da3c6647ee0871 Lan Tianyu 2014-05-20 7
da3c6647ee0871 Lan Tianyu 2014-05-20 @8 config I2C
^1da177e4c3f41 Linus Torvalds 2005-04-16 9 tristate "I2C support"
194684e596af4b Mika Kuoppala 2009-12-06 10 select RT_MUTEXES
4d5538f5882a6b Benjamin Tissoires 2016-10-13 11 select IRQ_DOMAIN
a7f7f6248d9740 Masahiro Yamada 2020-06-14 12 help
622e040d577dc8 Michael Witten 2011-07-08 13 I2C (pronounce: I-squared-C) is a slow serial bus protocol used in
^1da177e4c3f41 Linus Torvalds 2005-04-16 14 many micro controller applications and developed by Philips. SMBus,
^1da177e4c3f41 Linus Torvalds 2005-04-16 15 or System Management Bus is a subset of the I2C protocol. More
^1da177e4c3f41 Linus Torvalds 2005-04-16 16 information is contained in the directory <file:Documentation/i2c/>,
^1da177e4c3f41 Linus Torvalds 2005-04-16 17 especially in the file called "summary" there.
^1da177e4c3f41 Linus Torvalds 2005-04-16 18
^1da177e4c3f41 Linus Torvalds 2005-04-16 19 Both I2C and SMBus are supported here. You will need this for
^1da177e4c3f41 Linus Torvalds 2005-04-16 20 hardware sensors support, and also for Video For Linux support.
^1da177e4c3f41 Linus Torvalds 2005-04-16 21
^1da177e4c3f41 Linus Torvalds 2005-04-16 22 If you want I2C support, you should say Y here and also to the
^1da177e4c3f41 Linus Torvalds 2005-04-16 23 specific driver for your bus adapter(s) below.
^1da177e4c3f41 Linus Torvalds 2005-04-16 24
^1da177e4c3f41 Linus Torvalds 2005-04-16 25 This I2C support can also be built as a module. If so, the module
^1da177e4c3f41 Linus Torvalds 2005-04-16 26 will be called i2c-core.
^1da177e4c3f41 Linus Torvalds 2005-04-16 27
---
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: 16144 bytes --]
next prev parent reply other threads:[~2020-12-07 22:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 20:48 [PATCH v3] drivers: gpio: add virtio-gpio guest driver Enrico Weigelt, metux IT consult
2020-12-07 22:13 ` kernel test robot [this message]
2020-12-07 22:40 ` kernel test robot
2020-12-07 23:03 ` Randy Dunlap
2020-12-08 1:20 ` Randy Dunlap
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=202012080644.2LjqW7Sc-lkp@intel.com \
--to=lkp@intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=corbet@lwn.net \
--cc=info@metux.net \
--cc=jasowang@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).