From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: kernel test robot <lkp@intel.com>
Cc: Yangtao Li <tiny.windzz@gmail.com>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Thierry Reding <thierry.reding@gmail.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Subject: Re: [linux-next:master 4170/7280] pwm-brcmstb.c:undefined reference to `devm_platform_ioremap_resource'
Date: Fri, 20 Nov 2020 13:57:11 +0100 [thread overview]
Message-ID: <20201120125711.h3afnz2vz6ebkvp4@pengutronix.de> (raw)
In-Reply-To: <202011202042.QpDIUcES-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2486 bytes --]
On Fri, Nov 20, 2020 at 08:33:46PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 95065cb54210eba86bed10cb2118041524d54573
> commit: 0e74dcd8333d794fdbc4bef69d17431404a01a6f [4170/7280] pwm: brcmstb: Convert to devm_platform_ioremap_resource()
> config: s390-randconfig-r034-20201120 (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
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=0e74dcd8333d794fdbc4bef69d17431404a01a6f
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout 0e74dcd8333d794fdbc4bef69d17431404a01a6f
> # 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>
>
> Note: the linux-next/master HEAD 95065cb54210eba86bed10cb2118041524d54573 builds fine.
> It may have been fixed somewhere.
This is indeed the case,
ffc32cb0e1f6 pwm: Fix dependencies on HAS_IOMEM
is supposed to fix this.
> s390-linux-ld: drivers/pwm/pwm-brcmstb.o: in function `brcmstb_pwm_probe':
> >> pwm-brcmstb.c:(.text+0x466): undefined reference to `devm_platform_ioremap_resource'
I expect that before the blamed commit (0e74dcd8333d ("pwm: brcmstb:
Convert to devm_platform_ioremap_resource()")) the driver failed with:
pwm-brcmstb.c:(.text+0xfoo): undefined reference to `devm_ioremap_resource'
so it probably makes little sense to ensure the commit "pwm: Fix
dependencies on HAS_IOMEM" comes before "pwm: brcmstb: Convert to
devm_platform_ioremap_resource()" (and the other similar conversions).
The only upside of rewriting the pwm-next tree would be that
autobuilders wouldn't stumble because the error changed. Hardly good
enough a reason, still more as the dependency is missing for quite some
time already I guess.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-11-20 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 12:33 kernel test robot
2020-11-20 12:57 ` Uwe Kleine-König [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=20201120125711.h3afnz2vz6ebkvp4@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=nsaenzjulienne@suse.de \
--cc=thierry.reding@gmail.com \
--cc=tiny.windzz@gmail.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