From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC v3 2/6] mmc: core: allow to match the device tree to apply quirks
Date: Thu, 04 Nov 2021 01:57:27 +0800 [thread overview]
Message-ID: <202111040122.26FpYuIq-lkp@intel.com> (raw)
In-Reply-To: <e6a52b238af3022b9a3dad7cad29b632fa34c00b.1635944413.git.hns@goldelico.com>
[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]
Hi Nikolaus,
[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on ulf-hansson-mmc-mirror/next]
[also build test ERROR on v5.15 next-20211103]
[cannot apply to linus/master]
[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/H-Nikolaus-Schaller/mmc-core-extend-mmc_fixup_device-and-transplant-ti-wl1251-quirks-from-to-be-retired-omap_hsmmc/20211103-210343
base: https://git.linaro.org/people/ulf.hansson/mmc-mirror.git next
config: i386-randconfig-c001-20211103 (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/e34268c772dc58fd4126815d1a0ce277b6ecc4f9
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review H-Nikolaus-Schaller/mmc-core-extend-mmc_fixup_device-and-transplant-ti-wl1251-quirks-from-to-be-retired-omap_hsmmc/20211103-210343
git checkout e34268c772dc58fd4126815d1a0ce277b6ecc4f9
# save the attached .config to linux build tree
make W=1 ARCH=i386
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 >>, old ones prefixed by <<):
>> ERROR: modpost: "of_device_compatible_match" [drivers/mmc/core/mmc_block.ko] undefined!
>> ERROR: modpost: "mmc_of_find_child_device" [drivers/mmc/core/mmc_block.ko] undefined!
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 32367 bytes --]
next prev parent reply other threads:[~2021-11-03 17:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 13:00 [RFC v3 0/6] mmc: core: extend mmc_fixup_device and transplant ti,wl1251 quirks from to be retired omap_hsmmc H. Nikolaus Schaller
2021-11-03 13:00 ` [RFC v3 1/6] mmc: core: rewrite mmc_fixup_device() H. Nikolaus Schaller
2021-11-09 11:15 ` Linus Walleij
2021-11-03 13:00 ` [RFC v3 2/6] mmc: core: allow to match the device tree to apply quirks H. Nikolaus Schaller
2021-11-03 13:24 ` Jérôme Pouiller
2021-11-03 13:36 ` H. Nikolaus Schaller
2021-11-03 17:57 ` kernel test robot [this message]
2021-11-09 11:16 ` Linus Walleij
2021-11-03 13:00 ` [RFC v3 3/6] mmc: core: provide macro and table " H. Nikolaus Schaller
2021-11-09 11:17 ` Linus Walleij
2021-11-03 13:00 ` [RFC v3 4/6] mmc: core: add new calls to mmc_fixup_device(sdio_card_init_methods) H. Nikolaus Schaller
2021-11-09 11:18 ` Linus Walleij
2021-11-03 13:00 ` [RFC v3 5/6] mmc: core: transplant ti,wl1251 quirks from to be retired omap_hsmmc H. Nikolaus Schaller
2021-11-09 11:19 ` Linus Walleij
2021-11-03 13:00 ` [RFC v3 6/6] mmc: host: omap_hsmmc: revert special init for wl1251 H. Nikolaus Schaller
2021-11-09 11:20 ` Linus Walleij
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=202111040122.26FpYuIq-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.