From: Krzysztof Kozlowski <krzk@kernel.org>
To: kbuild-all@lists.01.org
Subject: Re: ERROR: "ap_driver_register" undefined!
Date: Wed, 05 Aug 2020 10:13:40 +0200 [thread overview]
Message-ID: <20200805080809.GA5268@pi3> (raw)
In-Reply-To: <202008042249.EnHi1w22%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
On Tue, Aug 04, 2020 at 10:29:53PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: c0842fbc1b18c7a044e6ff3e8fa78bfa822c7d1a
> commit: e93a1695d7fb551376b1c1220a267d032b6ad159 iommu: Enable compile testing for some of drivers
> date: 5 months ago
> config: s390-randconfig-m031-20200804 (attached as .config)
> compiler: s390-linux-gcc (GCC) 9.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
> git checkout e93a1695d7fb551376b1c1220a267d032b6ad159
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=s390
>
> 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 >>):
>
> >> ERROR: "ap_driver_register" [drivers/s390/crypto/vfio_ap.ko] undefined!
> >> ERROR: "ap_driver_unregister" [drivers/s390/crypto/vfio_ap.ko] undefined!
I have a fix for this ready. I'll send it soon.
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Joerg Roedel <jroedel@suse.de>
Subject: Re: ERROR: "ap_driver_register" undefined!
Date: Wed, 5 Aug 2020 10:13:40 +0200 [thread overview]
Message-ID: <20200805080809.GA5268@pi3> (raw)
In-Reply-To: <202008042249.EnHi1w22%lkp@intel.com>
On Tue, Aug 04, 2020 at 10:29:53PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: c0842fbc1b18c7a044e6ff3e8fa78bfa822c7d1a
> commit: e93a1695d7fb551376b1c1220a267d032b6ad159 iommu: Enable compile testing for some of drivers
> date: 5 months ago
> config: s390-randconfig-m031-20200804 (attached as .config)
> compiler: s390-linux-gcc (GCC) 9.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
> git checkout e93a1695d7fb551376b1c1220a267d032b6ad159
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=s390
>
> 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 >>):
>
> >> ERROR: "ap_driver_register" [drivers/s390/crypto/vfio_ap.ko] undefined!
> >> ERROR: "ap_driver_unregister" [drivers/s390/crypto/vfio_ap.ko] undefined!
I have a fix for this ready. I'll send it soon.
Best regards,
Krzysztof
next prev parent reply other threads:[~2020-08-05 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 14:29 ERROR: "ap_driver_register" undefined! kernel test robot
2020-08-04 14:29 ` kernel test robot
2020-08-05 8:13 ` Krzysztof Kozlowski [this message]
2020-08-05 8:13 ` Krzysztof Kozlowski
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=20200805080809.GA5268@pi3 \
--to=krzk@kernel.org \
--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.