From: Michal Simek <michal.simek@xilinx.com>
To: Brendan Higgins <brendanhiggins@google.com>,
kernel test robot <lkp@intel.com>,
radheys@xilinx.com
Cc: kbuild-all@lists.01.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
David Gow <davidgow@google.com>,
netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: xilinx_axienet_main.c:undefined reference to `devm_ioremap_resource'
Date: Wed, 24 Jun 2020 08:40:05 +0200 [thread overview]
Message-ID: <a3345aaa-ca17-d37c-73aa-c1b03f9cec3e@xilinx.com> (raw)
In-Reply-To: <CAFd5g44jTP9qtYE1knkRzwTWATKfZREWDrTn=T_WwZEGkNSemw@mail.gmail.com>
On 23. 06. 20 23:27, Brendan Higgins wrote:
> On Sat, Jun 20, 2020 at 1:59 AM kernel test robot <lkp@intel.com> wrote:
>>
>> Hi Brendan,
>>
>> It's probably a bug fix that unveils the link errors.
>>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: 4333a9b0b67bb4e8bcd91bdd80da80b0ec151162
>> commit: 1af73a25e6e7d9f2f1e2a14259cc9ffce6d8f6d4 staging: exfat: fix multiple definition error of `rename_file'
>> date: 6 months ago
>> config: um-allyesconfig (attached as .config)
>> compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
>> reproduce (this is a W=1 build):
>> git checkout 1af73a25e6e7d9f2f1e2a14259cc9ffce6d8f6d4
>> # save the attached .config to linux build tree
>> make W=1 ARCH=um
>>
>> 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 >>):
>>
>> /usr/bin/ld: drivers/net/ethernet/xilinx/xilinx_axienet_main.o: in function `axienet_probe':
>>>> xilinx_axienet_main.c:(.text+0x1aa6): undefined reference to `devm_ioremap_resource'
>>>> /usr/bin/ld: xilinx_axienet_main.c:(.text+0x1d06): undefined reference to `devm_ioremap_resource'
>> /usr/bin/ld: xilinx_axienet_main.c:(.text+0x2001): undefined reference to `devm_ioremap_resource'
>> collect2: error: ld returned 1 exit status
>
> I posted a fix for this months ago:
>
> https://patchwork.ozlabs.org/project/linux-um/patch/20191211192742.95699-4-brendanhiggins@google.com/
>
> I thought it got picked up by the maintainer.
>
Can you please send it again?
Thanks,
Michal
prev parent reply other threads:[~2020-06-24 6:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 8:58 kernel test robot
2020-06-23 21:27 ` Brendan Higgins
2020-06-24 6:40 ` Michal Simek [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=a3345aaa-ca17-d37c-73aa-c1b03f9cec3e@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=brendanhiggins@google.com \
--cc=davem@davemloft.net \
--cc=davidgow@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=radheys@xilinx.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
all inboxes | Powered by JetHome®