From: kernel test robot <lkp@intel.com>
To: frank zago <frank@zago.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Wolfram Sang <wsa-dev@sang-engineering.com>,
Johan Hovold <johan@kernel.org>,
linux-usb@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-i2c@vger.kernel.org
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH v6 3/4] i2c: ch341: add I2C MFD cell driver for the CH341
Date: Thu, 16 Jun 2022 19:10:53 +0800 [thread overview]
Message-ID: <202206161938.BiOHSAOi-lkp@intel.com> (raw)
In-Reply-To: <20220616013747.126051-4-frank@zago.net>
Hi frank,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on lee-mfd/for-mfd-next]
[also build test ERROR on brgl/gpio/for-next wsa/i2c/for-next linus/master v5.19-rc2 next-20220616]
[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/intel-lab-lkp/linux/commits/frank-zago/add-driver-for-the-WCH-CH341-in-I2C-GPIO-mode/20220616-094113
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
config: arc-buildonly-randconfig-r004-20220616 (https://download.01.org/0day-ci/archive/20220616/202206161938.BiOHSAOi-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 11.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/intel-lab-lkp/linux/commit/46c68aee86d34ee630272146a73ad7c3147bb094
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review frank-zago/add-driver-for-the-WCH-CH341-in-I2C-GPIO-mode/20220616-094113
git checkout 46c68aee86d34ee630272146a73ad7c3147bb094
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=arc SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
>> ERROR: modpost: "usb_bulk_msg" [drivers/i2c/busses/i2c-ch341.ko] undefined!
>> ERROR: modpost: "usb_deregister" [drivers/mfd/ch341-core.ko] undefined!
>> ERROR: modpost: "usb_register_driver" [drivers/mfd/ch341-core.ko] undefined!
>> ERROR: modpost: "usb_find_common_endpoints" [drivers/mfd/ch341-core.ko] undefined!
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for MFD_CH341
Depends on HAS_IOMEM && USB
Selected by
- I2C_CH341 && I2C && HAS_IOMEM
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-06-16 11:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 1:37 [PATCH v6 0/4] add driver for the WCH CH341 in I2C/GPIO mode frank zago
2022-06-16 1:37 ` [PATCH v6 1/4] mfd: ch341: add core driver for the WCH CH341 in I2C/SPI/GPIO mode frank zago
2022-06-27 14:04 ` Lee Jones
2022-06-27 14:28 ` Greg Kroah-Hartman
2022-06-27 14:43 ` Lee Jones
2022-06-27 23:30 ` Frank Zago
2022-07-04 10:09 ` Lee Jones
2022-06-16 1:37 ` [PATCH v6 2/4] gpio: ch341: add GPIO MFD cell driver for the CH341 frank zago
2022-06-17 8:29 ` Linus Walleij
2022-06-20 10:25 ` Johan Hovold
2022-06-20 16:08 ` Andy Shevchenko
2022-06-21 6:57 ` Johan Hovold
2022-06-16 1:37 ` [PATCH v6 3/4] i2c: ch341: add I2C " frank zago
2022-06-16 5:09 ` Randy Dunlap
2022-06-16 9:18 ` kernel test robot
2022-06-16 11:10 ` kernel test robot [this message]
2022-06-16 1:37 ` [PATCH v6 4/4] docs: misc: add documentation for ch341 driver frank zago
2022-06-20 10:08 ` [PATCH v6 0/4] add driver for the WCH CH341 in I2C/GPIO mode Johan Hovold
2024-11-08 15:58 ` Matwey V. Kornilov
2024-11-08 19:11 ` Linus Walleij
2024-11-08 23:15 ` Frank Zago
2024-11-09 7:32 ` Matwey V. Kornilov
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=202206161938.BiOHSAOi-lkp@intel.com \
--to=lkp@intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=frank@zago.net \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=wsa-dev@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).