From: kernel test robot <lkp@intel.com>
To: Jim Liu <jim.t90615@gmail.com>,
JJLIU0@nuvoton.com, krzysztof.kozlowski+dt@linaro.org,
linus.walleij@linaro.org, andy@kernel.org, robh+dt@kernel.org,
conor+dt@kernel.org, KWLIU@nuvoton.com
Cc: openbmc@lists.ozlabs.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v8 3/3] gpio: nuvoton: Add Nuvoton NPCM sgpio driver
Date: Thu, 7 Dec 2023 08:16:59 +0800 [thread overview]
Message-ID: <202312070733.GNrG7abU-lkp@intel.com> (raw)
In-Reply-To: <20231206014530.1600151-4-jim.t90615@gmail.com>
Hi Jim,
kernel test robot noticed the following build warnings:
[auto build test WARNING on brgl/gpio/for-next]
[also build test WARNING on robh/for-next linus/master v6.7-rc4 next-20231206]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Jim-Liu/dt-bindings-gpio-add-NPCM-sgpio-driver-bindings/20231206-095724
base: https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
patch link: https://lore.kernel.org/r/20231206014530.1600151-4-jim.t90615%40gmail.com
patch subject: [PATCH v8 3/3] gpio: nuvoton: Add Nuvoton NPCM sgpio driver
config: nios2-randconfig-r131-20231207 (https://download.01.org/0day-ci/archive/20231207/202312070733.GNrG7abU-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231207/202312070733.GNrG7abU-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312070733.GNrG7abU-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/gpio/gpio-npcm-sgpio.c:150:17: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected struct device const *dev @@ got int @@
drivers/gpio/gpio-npcm-sgpio.c:150:17: sparse: expected struct device const *dev
drivers/gpio/gpio-npcm-sgpio.c:150:17: sparse: got int
>> drivers/gpio/gpio-npcm-sgpio.c:150:17: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected struct device const *dev @@ got int @@
drivers/gpio/gpio-npcm-sgpio.c:150:17: sparse: expected struct device const *dev
drivers/gpio/gpio-npcm-sgpio.c:150:17: sparse: got int
>> drivers/gpio/gpio-npcm-sgpio.c:152:16: sparse: sparse: Using plain integer as NULL pointer
>> drivers/gpio/gpio-npcm-sgpio.c:534:20: sparse: sparse: incorrect type in initializer (different modifiers) @@ expected unsigned int *sft_clk @@ got unsigned int const * @@
drivers/gpio/gpio-npcm-sgpio.c:534:20: sparse: expected unsigned int *sft_clk
drivers/gpio/gpio-npcm-sgpio.c:534:20: sparse: got unsigned int const *
>> drivers/gpio/gpio-npcm-sgpio.c:535:20: sparse: sparse: incorrect type in initializer (different modifiers) @@ expected unsigned int *clk_sel @@ got unsigned int const * @@
drivers/gpio/gpio-npcm-sgpio.c:535:20: sparse: expected unsigned int *clk_sel
drivers/gpio/gpio-npcm-sgpio.c:535:20: sparse: got unsigned int const *
drivers/gpio/gpio-npcm-sgpio.c:540:20: sparse: sparse: incorrect type in initializer (different modifiers) @@ expected unsigned int *sft_clk @@ got unsigned int const * @@
drivers/gpio/gpio-npcm-sgpio.c:540:20: sparse: expected unsigned int *sft_clk
drivers/gpio/gpio-npcm-sgpio.c:540:20: sparse: got unsigned int const *
drivers/gpio/gpio-npcm-sgpio.c:541:20: sparse: sparse: incorrect type in initializer (different modifiers) @@ expected unsigned int *clk_sel @@ got unsigned int const * @@
drivers/gpio/gpio-npcm-sgpio.c:541:20: sparse: expected unsigned int *clk_sel
drivers/gpio/gpio-npcm-sgpio.c:541:20: sparse: got unsigned int const *
vim +150 drivers/gpio/gpio-npcm-sgpio.c
134
135 static void __iomem *bank_reg(struct npcm_sgpio *gpio,
136 const struct npcm_sgpio_bank *bank,
137 const enum npcm_sgpio_reg reg)
138 {
139 switch (reg) {
140 case READ_DATA:
141 return gpio->base + bank->rdata_reg;
142 case WRITE_DATA:
143 return gpio->base + bank->wdata_reg;
144 case EVENT_CFG:
145 return gpio->base + bank->event_config;
146 case EVENT_STS:
147 return gpio->base + bank->event_status;
148 default:
149 /* actually if code runs to here, it's an error case */
> 150 dev_WARN(true, "Getting here is an error condition");
151 }
> 152 return 0;
153 }
154
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-12-07 0:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 1:45 [PATCH v8 0/3] Add Nuvoton NPCM SGPIO feature Jim Liu
2023-12-06 1:45 ` [PATCH v8 1/3] dt-bindings: gpio: add NPCM sgpio driver bindings Jim Liu
2023-12-06 1:45 ` [PATCH v8 2/3] arm: dts: nuvoton: npcm: Add sgpio feature Jim Liu
2023-12-06 1:45 ` [PATCH v8 3/3] gpio: nuvoton: Add Nuvoton NPCM sgpio driver Jim Liu
2023-12-06 12:28 ` kernel test robot
2023-12-07 0:16 ` kernel 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=202312070733.GNrG7abU-lkp@intel.com \
--to=lkp@intel.com \
--cc=JJLIU0@nuvoton.com \
--cc=KWLIU@nuvoton.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jim.t90615@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).