From: "Stefan Mätje" <Stefan.Maetje@esd.eu>
To: "lkp@intel.com" <lkp@intel.com>,
"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
"wg@grandegger.com" <wg@grandegger.com>,
"mkl@pengutronix.de" <mkl@pengutronix.de>
Cc: "kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] can: esd: add support for esd GmbH PCIe/402 CAN interface family
Date: Thu, 16 Sep 2021 17:47:22 +0000 [thread overview]
Message-ID: <d05c727fb91f598a28e7fc8e5fcc5643ea5ab93c.camel@esd.eu> (raw)
In-Reply-To: <202109120608.7ZbQXkRh-lkp@intel.com>
Am Sonntag, den 12.09.2021, 07:00 +0800 schrieb kernel test robot:
> Hi "Stefan,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on cbe8cd7d83e251bff134a57ea4b6378db992ad82]
>
> url:
> https://github.com/0day-ci/linux/commits/Stefan-M-tje/can-esd-add-support-for-esd-GmbH-PCIe-402-CAN-interface/20210909-004948
> base: cbe8cd7d83e251bff134a57ea4b6378db992ad82
> config: arm64-randconfig-r033-20210911 (attached as .config)
> compiler: aarch64-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/f2b8372d3e4a1cb2ece97f52560d0a598b36cb6b
> git remote add linux-review https://github.com/0day-ci/linux
> git fetch --no-tags linux-review Stefan-M-tje/can-esd-add-support-for-esd-GmbH-PCIe-402-CAN-interface/20210909-004948
> git checkout f2b8372d3e4a1cb2ece97f52560d0a598b36cb6b
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=arm64
>
> 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: "__aarch64_ldadd4_acq_rel" [drivers/net/can/esd/esd_402_pci.ko] undefined!
This issue has been fixed in v4 of the patch. See
https://lore.kernel.org/linux-can/20210916172152.5127-1-stefan.maetje@esd.eu/
--
Best regards,
Stefan Mätje
System Design
Phone: +49-511-37298-146
E-Mail: stefan.maetje@esd.eu
_______________________________________
esd electronics gmbh
Vahrenwalder Str. 207
30165 Hannover
www.esd.eu
Quality Products – Made in Germany
_______________________________________
Register Hannover HRB 51373 - VAT-ID DE 115672832
General Manager: Klaus Detering
prev parent reply other threads:[~2021-09-16 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 16:46 [PATCH v3 0/2] can: esd: add support for esd GmbH PCIe/402 CAN interface Stefan Mätje
2021-09-08 16:46 ` [PATCH v3 1/2] MAINTAINERS: add Stefan Mätje as maintainer for the esd electronics GmbH CAN drivers Stefan Mätje
2021-09-08 16:46 ` [PATCH v3 2/2] can: esd: add support for esd GmbH PCIe/402 CAN interface family Stefan Mätje
2021-09-11 23:00 ` kernel test robot
2021-09-16 17:47 ` Stefan Mätje [this message]
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=d05c727fb91f598a28e7fc8e5fcc5643ea5ab93c.camel@esd.eu \
--to=stefan.maetje@esd.eu \
--cc=kbuild-all@lists.01.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=wg@grandegger.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).