From: kbuild test robot <lkp@intel.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: kbuild-all@01.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/of: Add devm_of_iomap()
Date: Thu, 14 Jun 2018 21:30:45 +0800 [thread overview]
Message-ID: <201806142128.gPVVai7X%fengguang.wu@intel.com> (raw)
In-Reply-To: <23be2945b593a36d8fa1970bb579389c0f892a3e.camel@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 2463 bytes --]
Hi Benjamin,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17 next-20180614]
[cannot apply to glikely/devicetree/next]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Benjamin-Herrenschmidt/drivers-of-Add-devm_of_iomap/20180612-080800
config: um-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=um
All errors (new ones prefixed by >>):
arch/um/drivers/vde.o: In function `vde_open_real':
(.text+0x951): warning: Using 'getgrnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
(.text+0x79c): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
arch/um/drivers/vector_user.o: In function `user_init_socket_fds':
vector_user.c:(.text+0x334): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
arch/um/drivers/pcap.o: In function `pcap_nametoaddr':
(.text+0xdee5): warning: Using 'gethostbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
arch/um/drivers/pcap.o: In function `pcap_nametonetaddr':
(.text+0xdf85): warning: Using 'getnetbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
arch/um/drivers/pcap.o: In function `pcap_nametoproto':
(.text+0xe1a5): warning: Using 'getprotobyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
arch/um/drivers/pcap.o: In function `pcap_nametoport':
(.text+0xdfd7): warning: Using 'getservbyname' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
drivers/of/address.o: In function `devm_of_iomap':
>> (.text+0x1882): undefined reference to `devm_ioremap_resource'
collect2: error: ld returned 1 exit status
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 19601 bytes --]
prev parent reply other threads:[~2018-06-14 13:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 0:01 Benjamin Herrenschmidt
2018-06-12 8:35 ` Andy Shevchenko
2018-06-12 10:28 ` Benjamin Herrenschmidt
2018-06-12 16:53 ` Andy Shevchenko
2018-06-12 22:58 ` Benjamin Herrenschmidt
2018-06-12 23:16 ` Andy Shevchenko
2018-06-13 0:18 ` Benjamin Herrenschmidt
2018-06-13 8:18 ` Andy Shevchenko
2018-06-12 17:42 ` Rob Herring
2018-06-12 22:53 ` Benjamin Herrenschmidt
2018-06-13 15:00 ` Rob Herring
2018-06-13 23:07 ` Benjamin Herrenschmidt
2018-06-14 8:27 ` Geert Uytterhoeven
2018-06-14 23:50 ` Benjamin Herrenschmidt
2018-06-15 6:16 ` Geert Uytterhoeven
2018-06-15 6:52 ` Benjamin Herrenschmidt
2018-06-14 13:30 ` kbuild test robot [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=201806142128.gPVVai7X%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.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 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®