From: kernel test robot <lkp@intel.com>
To: Lars Povlsen <lars.povlsen@microchip.com>,
Arnd Bergmann <arnd@arndb.de>, Stephen Boyd <sboyd@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: kbuild-all@lists.01.org,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
Olof Johansson <olof@lixom.net>,
Michael Turquette <mturquette@baylibre.com>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 05/10] pinctrl: ocelot: Add Sparx5 SoC support
Date: Tue, 9 Jun 2020 21:07:28 +0800 [thread overview]
Message-ID: <202006092013.1bzkFJvZ%lkp@intel.com> (raw)
In-Reply-To: <20200609080709.9654-5-lars.povlsen@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
Hi Lars,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on next-20200608]
[cannot apply to robh/for-next clk/clk-next pinctrl/devel v5.7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Lars-Povlsen/Adding-support-for-Microchip-Sparx5-SoC/20200609-161131
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git abfbb29297c27e3f101f348dc9e467b0fe70f919
config: x86_64-randconfig-s021-20200607 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-247-gcadbd124-dirty
# save the attached .config to linux build tree
make W=1 C=1 ARCH=x86_64 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/pinctrl/pinctrl-ocelot.c:785:14: sparse: sparse: symbol 'ocelot_pinconf_set' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 50211 bytes --]
next prev parent reply other threads:[~2020-06-09 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 12:30 [PATCH v2 00/10] Adding support for Microchip Sparx5 SoC Lars Povlsen
2020-06-09 8:07 ` [PATCH v2 01/10] dt-bindings: arm: sparx5: Add documentation " Lars Povlsen
2020-06-09 8:07 ` [PATCH v2 02/10] arm64: sparx5: Add support for Microchip 2xA53 SoC Lars Povlsen
2020-06-09 8:07 ` [PATCH v2 03/10] arm64: dts: sparx5: Add basic cpu support Lars Povlsen
2020-06-09 8:07 ` [PATCH v2 04/10] arm64: dts: sparx5: Add pinctrl support Lars Povlsen
2020-06-09 8:07 ` [PATCH v2 05/10] pinctrl: ocelot: Add Sparx5 SoC support Lars Povlsen
2020-06-09 10:31 ` kernel test robot
2020-06-09 13:07 ` kernel test robot [this message]
2020-06-09 13:07 ` [RFC PATCH] pinctrl: ocelot: ocelot_pinconf_set() can be static kernel test robot
2020-06-09 8:07 ` [PATCH v2 06/10] dt-bindings: clock: sparx5: Add Sparx5 SoC DPLL clock Lars Povlsen
2020-06-09 8:07 ` [PATCH v2 07/10] dt-bindings: clock: sparx5: Add bindings include file Lars Povlsen
2020-06-09 8:07 ` [PATCH v2 08/10] clk: sparx5: Add Sparx5 SoC DPLL clock driver Lars Povlsen
2020-06-09 8:07 ` [PATCH v2 09/10] arm64: dts: sparx5: Add Sparx5 SoC DPLL clock Lars Povlsen
2020-06-09 8:07 ` [PATCH v2 10/10] arm64: dts: sparx5: Add i2c devices, i2c muxes Lars Povlsen
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=202006092013.1bzkFJvZ%lkp@intel.com \
--to=lkp@intel.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=lars.povlsen@microchip.com \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=olof@lixom.net \
--cc=sboyd@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