From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: zhuyinbo <zhuyinbo@loongson.cn>
Cc: kernel test robot <lkp@intel.com>,
Minas Harutyunyan <hminas@synopsys.com>,
Bjorn Helgaas <helgaas@kernel.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
Jianmin Lv <lvjianmin@loongson.cn>,
wanghongliang@loongson.cn, Liu Peibao <liupeibao@loongson.cn>,
loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH v1] usb: dwc2: add pci_device_id driver_data parse support
Date: Fri, 19 May 2023 10:49:15 +0100 [thread overview]
Message-ID: <2023051951-snuff-fit-4cf6@gregkh> (raw)
In-Reply-To: <933c829f-0d27-f3b9-3db6-f2211495b086@loongson.cn>
On Fri, May 19, 2023 at 03:13:20PM +0800, zhuyinbo wrote:
>
>
> 在 2023/5/19 上午1:52, kernel test robot 写道:
> > Hi Yinbo,
> >
> > kernel test robot noticed the following build errors:
> >
> > [auto build test ERROR on pci/next]
> > [also build test ERROR on pci/for-linus westeri-thunderbolt/next linus/master v6.4-rc2 next-20230518]
> > [cannot apply to usb/usb-testing usb/usb-next usb/usb-linus]
> > [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#_base_tree_information]
> >
> > url: https://github.com/intel-lab-lkp/linux/commits/Yinbo-Zhu/usb-dwc2-add-pci_device_id-driver_data-parse-support/20230518-173721
> > base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
> > patch link: https://lore.kernel.org/r/20230518092240.8023-1-zhuyinbo%40loongson.cn
> > patch subject: [PATCH v1] usb: dwc2: add pci_device_id driver_data parse support
> > config: powerpc-allmodconfig
> > compiler: powerpc-linux-gcc (GCC) 12.1.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/3ff56448e1442fe8b1e72651a8d4d6e1086ece32
> > git remote add linux-review https://github.com/intel-lab-lkp/linux
> > git fetch --no-tags linux-review Yinbo-Zhu/usb-dwc2-add-pci_device_id-driver_data-parse-support/20230518-173721
> > git checkout 3ff56448e1442fe8b1e72651a8d4d6e1086ece32
> > # save the config file
> > mkdir build_dir && cp config build_dir/.config
> > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=powerpc olddefconfig
> > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=powerpc SHELL=/bin/bash
> >
> > If you fix the issue, kindly add following tag where applicable
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202305190105.O6ycxCti-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>, old ones prefixed by <<):
> >
> > > > ERROR: modpost: "dwc2_pci_ids" [drivers/usb/dwc2/dwc2_pci.ko] undefined!
>
>
> I test it was set dwc2 pci driver as built-in, so no error, this compile
> error was that dwc2_pci_ids not export when driver as module and I will
> add EXPORT_SYMBOL_GPL(dwc2_pci_ids) to fix that compile issue.
Again, no, please do this properly, no one should ever be walking a pci
id list by hand like this...
thanks,
greg k-h
next prev parent reply other threads:[~2023-05-19 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 9:22 [PATCH v1] usb: dwc2: add pci_device_id driver_data parse support Yinbo Zhu
2023-05-18 10:32 ` Greg Kroah-Hartman
2023-05-20 3:24 ` zhuyinbo
2023-06-08 7:54 ` zhuyinbo
2023-06-08 8:01 ` Greg Kroah-Hartman
2023-06-08 8:57 ` zhuyinbo
2023-06-08 9:11 ` Greg Kroah-Hartman
2023-06-09 1:15 ` zhuyinbo
2023-05-18 17:52 ` kernel test robot
2023-05-19 7:13 ` zhuyinbo
2023-05-19 9:49 ` Greg Kroah-Hartman [this message]
2023-05-20 3:33 ` zhuyinbo
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=2023051951-snuff-fit-4cf6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=hminas@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=liupeibao@loongson.cn \
--cc=lkp@intel.com \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=lvjianmin@loongson.cn \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wanghongliang@loongson.cn \
--cc=zhuyinbo@loongson.cn \
/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