From: Matthias Kaehlcke <mka@chromium.org>
To: kernel test robot <lkp@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Felipe Balbi <balbi@kernel.org>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Peter Chen <peter.chen@kernel.org>
Subject: Re: [PATCH v17 1/7] usb: misc: Add onboard_usb_hub driver
Date: Thu, 18 Nov 2021 10:36:05 -0800 [thread overview]
Message-ID: <YZadFV6tuEyDKjgm@google.com> (raw)
In-Reply-To: <202111190233.KiLjufx1-lkp@intel.com>
On Fri, Nov 19, 2021 at 02:13:52AM +0800, kernel test robot wrote:
> Hi Matthias,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on robh/for-next]
> [also build test ERROR on driver-core/driver-core-testing linus/master v5.16-rc1 next-20211118]
> [cannot apply to usb/usb-testing]
> [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/Matthias-Kaehlcke/usb-misc-Add-onboard_usb_hub-driver/20211117-040918
> base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
> config: m68k-allmodconfig (attached as .config)
> compiler: m68k-linux-gcc (GCC) 11.2.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/faa2d834f6d4083b63ab466134738d1befaa83b6
> git remote add linux-review https://github.com/0day-ci/linux
> git fetch --no-tags linux-review Matthias-Kaehlcke/usb-misc-Add-onboard_usb_hub-driver/20211117-040918
> git checkout faa2d834f6d4083b63ab466134738d1befaa83b6
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=m68k
>
> 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: "device_is_bound" [drivers/usb/misc/onboard_usb_hub.ko] undefined!
Looks like device_is_bound() needs to be exported to use it from a module.
next prev parent reply other threads:[~2021-11-18 18:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 20:07 [PATCH v17 0/7] usb: misc: Add onboard_usb_hub driver Matthias Kaehlcke
2021-11-16 20:07 ` [PATCH v17 1/7] " Matthias Kaehlcke
2021-11-18 0:11 ` Doug Anderson
2021-11-18 17:52 ` Matthias Kaehlcke
2021-12-10 16:51 ` Matthias Kaehlcke
2021-11-18 18:13 ` kernel test robot
2021-11-18 18:36 ` Matthias Kaehlcke [this message]
2021-12-20 20:05 ` Dmitry Osipenko
2021-12-30 20:17 ` Matthias Kaehlcke
2022-01-01 12:23 ` Dmitry Osipenko
2022-01-12 19:00 ` Matthias Kaehlcke
2021-11-16 20:07 ` [PATCH v17 2/7] of/platform: Add stubs for of_platform_device_create/destroy() Matthias Kaehlcke
2021-11-22 17:43 ` Matthias Kaehlcke
2021-12-01 22:31 ` Matthias Kaehlcke
2021-11-16 20:07 ` [PATCH v17 3/7] usb: core: hcd: Create platform devices for onboard hubs in probe() Matthias Kaehlcke
2021-11-18 0:03 ` Doug Anderson
2021-11-16 20:07 ` [PATCH v17 4/7] arm64: dts: qcom: sc7180-trogdor: Add nodes for onboard USB hub Matthias Kaehlcke
2021-11-18 0:03 ` Doug Anderson
2021-11-18 18:43 ` Matthias Kaehlcke
2021-11-16 20:07 ` [PATCH v17 5/7] ARM: configs: Explicitly enable USB_XHCI_PLATFORM where needed Matthias Kaehlcke
2021-11-16 20:07 ` [PATCH v17 6/7] arm64: defconfig: Explicitly enable USB_XHCI_PLATFORM Matthias Kaehlcke
2021-11-16 20:07 ` [PATCH v17 7/7] usb: Specify dependencies on USB_XHCI_PLATFORM with 'depends on' Matthias Kaehlcke
2021-11-17 2:21 ` Alan Stern
2021-11-18 17:16 ` Matthias Kaehlcke
2021-12-16 23:56 ` Matthias Kaehlcke
2021-12-17 0:47 ` Dmitry Osipenko
2021-12-20 18:44 ` Matthias Kaehlcke
2021-12-20 19:59 ` Dmitry Osipenko
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=YZadFV6tuEyDKjgm@google.com \
--to=mka@chromium.org \
--cc=balbi@kernel.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mathias.nyman@intel.com \
--cc=peter.chen@kernel.org \
--cc=robh+dt@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=swboyd@chromium.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).