From: Rong Chen <rong.a.chen@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
kernel test robot <lkp@intel.com>,
Wang Hai <wanghai38@huawei.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] Re: s390-linux-ld: ll_temac_main.c:undefined reference to `devm_platform_ioremap_resource_byname'
Date: Tue, 2 Feb 2021 17:20:26 +0800 [thread overview]
Message-ID: <f297b20d-a2cc-88b0-2d8e-9f41c842ab83@intel.com> (raw)
In-Reply-To: <8044e33e-018a-839b-4f71-38510d576f6e@infradead.org>
On 2/2/21 1:22 PM, Randy Dunlap wrote:
> On 2/1/21 9:09 PM, Rong Chen wrote:
>>
>> On 2/2/21 6:38 AM, Randy Dunlap wrote:
>>> On 1/31/21 4:06 PM, kernel test robot wrote:
>>>> Hi Wang,
>>>>
>>>> FYI, the error/warning still remains.
>>>>
>>>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>>>> head: 1048ba83fb1c00cd24172e23e8263972f6b5d9ac
>>>> commit: bd69058f50d5ffa659423bcfa6fe6280ce9c760a net: ll_temac: Use devm_platform_ioremap_resource_byname()
>>>> date: 6 months ago
>>>> config: s390-randconfig-r034-20210201 (attached as .config)
>>> Hi robot,
>>>
>>> Instead of hit & miss with s390 randconfigs, you could do what I did:
>>> (all for arch/s390/):
>> Hi Randy,
>>
>> Thanks for the advice, do you mean we don't need to test randconfig for arch s390?
> You should still do randconfig testing for s390 (for other problems), but the robot has been
> sending out a lot of build errors similar to this one, using different randconfig files.
>
> I am just saying that you can find all of the ioremap/iounmap/devm_io* type build errors
> in one kernel config file as described above.
Hi Randy,
Thanks for the detailed explanation, will do it.
Best Regards,
Rong Chen
>
>> Best Regards,
>> Rong Chen
>>
>>> $ make allmodconfig
>>> $ scripts/config -d PCI ## this also disables HAS_IOMEM
>>> $ make oldconfig
>>> $ make all
>>>
>>> The latter gives a full list of drivers etc. that use iomemp/ioremap etc. as well as dev_io* variants instead of just a few random ones.
>>>
>>>
>>>> All errors (new ones prefixed by >>):
>>>>
>>>> s390-linux-ld: drivers/net/ethernet/xilinx/ll_temac_main.o: in function `temac_probe':
>>>> ll_temac_main.c:(.text+0x39b6): undefined reference to `devm_platform_ioremap_resource_byname'
>>>>>> s390-linux-ld: ll_temac_main.c:(.text+0x3a4c): undefined reference to `devm_platform_ioremap_resource_byname'
>>>> s390-linux-ld: ll_temac_main.c:(.text+0x3bce): undefined reference to `devm_ioremap'
>>>> s390-linux-ld: drivers/net/ethernet/xilinx/xilinx_axienet_main.o: in function `axienet_probe':
>>>> xilinx_axienet_main.c:(.text+0x844): undefined reference to `devm_ioremap_resource'
>>> _______________________________________________
>
prev parent reply other threads:[~2021-02-02 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 0:06 s390-linux-ld: ll_temac_main.c:undefined reference to `devm_platform_ioremap_resource_byname' kernel test robot
2021-02-01 22:38 ` Randy Dunlap
2021-02-02 5:09 ` [kbuild-all] " Rong Chen
2021-02-02 5:22 ` Randy Dunlap
2021-02-02 9:20 ` Rong Chen [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=f297b20d-a2cc-88b0-2d8e-9f41c842ab83@intel.com \
--to=rong.a.chen@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rdunlap@infradead.org \
--cc=wanghai38@huawei.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).