From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linus.walleij@linaro.org,
thierry.reding@gmail.com, jonathanh@nvidia.com,
linux-gpio@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, Stefan Agner <stefan@agner.ch>
Subject: Re: [PATCH 2/2] pinctrl: tegra: move probe to __init section
Date: Thu, 20 Sep 2018 11:28:44 +0800 [thread overview]
Message-ID: <201809201118.3umlpZRm%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180919012427.12439-2-stefan@agner.ch>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
Hi Stefan,
I love your patch! Perhaps something to improve:
[auto build test WARNING on tegra/for-next]
[also build test WARNING on v4.19-rc4 next-20180919]
[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/Stefan-Agner/pinctrl-tegra-do-not-export-tegra_pinctrl_probe/20180919-174106
base: https://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git for-next
config: arm64-allmodconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=arm64
All warnings (new ones prefixed by >>):
>> WARNING: vmlinux.o(.text+0x8acbf0): Section mismatch in reference from the function tegra210_pinctrl_probe() to the function .init.text:tegra_pinctrl_probe()
The function tegra210_pinctrl_probe() references
the function __init tegra_pinctrl_probe().
This is often because tegra210_pinctrl_probe lacks a __init
annotation or the annotation of tegra_pinctrl_probe is wrong.
---
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: 60995 bytes --]
next prev parent reply other threads:[~2018-09-20 3:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 1:24 [PATCH 1/2] pinctrl: tegra: do not export tegra_pinctrl_probe Stefan Agner
2018-09-19 1:24 ` [PATCH 2/2] pinctrl: tegra: move probe to __init section Stefan Agner
2018-09-20 3:28 ` kbuild test robot [this message]
2018-09-20 15:16 ` Linus Walleij
2018-09-20 18:15 ` Stefan Agner
2018-09-20 15:15 ` [PATCH 1/2] pinctrl: tegra: do not export tegra_pinctrl_probe Linus Walleij
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=201809201118.3umlpZRm%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=jonathanh@nvidia.com \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=stefan@agner.ch \
--cc=thierry.reding@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