From: kbuild test robot <lkp@intel.com>
To: Saravanan Sekar <sravanhome@gmail.com>
Cc: kbuild-all@01.org, manivannan.sadhasivam@linaro.org,
linus.walleij@linaro.org, robh+dt@kernel.org,
mark.rutland@arm.com, afaerber@suse.de, catalin.marinas@arm.com,
will.deacon@arm.com, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, pn@denx.de,
mp-cs@actions-semi.com, jeff.chen@actions-semi.com,
thomas.liau@actions-semi.com, linux@cubietech.com,
Saravanan Sekar <sravanhome@gmail.com>
Subject: Re: [PATCH v3 4/5] pinctrl: actions: Add Actions Semi S700 pinctrl driver
Date: Mon, 30 Jul 2018 06:00:44 +0800 [thread overview]
Message-ID: <201807300552.cJ0VSU1K%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180729200038.11795-5-sravanhome@gmail.com>
Hi Saravanan,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on pinctrl/devel]
[also build test WARNING on next-20180727]
[cannot apply to v4.18-rc6]
[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/Saravanan-Sekar/Add-Actions-Semi-S700-pinctrl-support/20180730-040252
base: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/pinctrl/actions/pinctrl-s700.c:228:31: sparse: symbol 's700_pads' was not declared. Should it be static?
>> drivers/pinctrl/actions/pinctrl-s700.c:1552:30: sparse: symbol 's700_functions' was not declared. Should it be static?
>> drivers/pinctrl/actions/pinctrl-s700.c:1700:20: sparse: symbol 's700_padinfo' was not declared. Should it be static?
drivers/pinctrl/actions/pinctrl-s700.c:1589:10: sparse: Initializer entry defined twice
drivers/pinctrl/actions/pinctrl-s700.c:1594:10: also defined here
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-07-29 22:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 18:25 [PATCH v2 0/5] Add Actions Semi S700 pinctrl support Saravanan Sekar
2018-07-29 18:25 ` [PATCH v2 1/5] pinctrl: actions: define constructor generic to Actions Semi SoC's Saravanan Sekar
2018-07-29 19:06 ` kbuild test robot
2018-07-29 19:12 ` kbuild test robot
2018-07-29 18:25 ` [PATCH v2 2/5] pinctrl: actions: define pad control configurtion to SoC specific Saravanan Sekar
2018-07-29 18:25 ` [PATCH v2 3/5] dt-bindings: pinctrl: Add bindings for Actions Semi S700 SoC Saravanan Sekar
2018-07-29 18:25 ` [PATCH v2 4/5] pinctrl: actions: Add Actions Semi S700 pinctrl driver Saravanan Sekar
2018-07-29 18:25 ` [PATCH v2 5/5] arm64: dts: actions: Add pinctrl node for Actions Semi S700 Saravanan Sekar
2018-07-29 21:26 ` kbuild test robot
2018-07-29 20:00 ` [PATCH v3 0/5] Add Actions Semi S700 pinctrl support Saravanan Sekar
2018-07-29 20:00 ` [PATCH v3 1/5] pinctrl: actions: define constructor generic to Actions Semi SoC's Saravanan Sekar
2018-07-29 20:00 ` [PATCH v3 2/5] pinctrl: actions: define pad control configurtion to SoC specific Saravanan Sekar
2018-07-29 20:00 ` [PATCH v3 3/5] dt-bindings: pinctrl: Add bindings for Actions Semi S700 SoC Saravanan Sekar
2018-07-30 23:18 ` Rob Herring
2018-07-29 20:00 ` [PATCH v3 4/5] pinctrl: actions: Add Actions Semi S700 pinctrl driver Saravanan Sekar
2018-07-29 22:00 ` kbuild test robot [this message]
2018-07-29 22:00 ` [RFC PATCH] pinctrl: actions: s700_pads[] can be static kbuild test robot
2018-07-29 20:00 ` [PATCH v3 5/5] arm64: dts: actions: Add pinctrl node for Actions Semi S700 Saravanan Sekar
2018-07-30 2:48 ` kbuild test robot
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=201807300552.cJ0VSU1K%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=afaerber@suse.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jeff.chen@actions-semi.com \
--cc=kbuild-all@01.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@cubietech.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mark.rutland@arm.com \
--cc=mp-cs@actions-semi.com \
--cc=pn@denx.de \
--cc=robh+dt@kernel.org \
--cc=sravanhome@gmail.com \
--cc=thomas.liau@actions-semi.com \
--cc=will.deacon@arm.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®