From: kernel test robot <lkp@intel.com>
To: Stanley Chu <stanley.chuys@gmail.com>,
alexandre.belloni@bootlin.com, robh@kernel.org,
krzk+dt@kernel.org, linux-i3c@lists.infradead.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org, tomer.maimon@nuvoton.com,
kwliu@nuvoton.com, yschu@nuvoton.com, cpchiang1@nuvoton.com
Subject: Re: [PATCH v1 2/2] i3c: master: Add Nuvoton npcm845 i3c master driver
Date: Sat, 3 Aug 2024 07:25:53 +0800 [thread overview]
Message-ID: <202408030639.LBZ5zgGw-lkp@intel.com> (raw)
In-Reply-To: <20240801071946.43266-3-yschu@nuvoton.com>
Hi Stanley,
kernel test robot noticed the following build errors:
[auto build test ERROR on robh/for-next]
[also build test ERROR on linus/master v6.11-rc1 next-20240802]
[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/Stanley-Chu/dt-bindings-i3c-Add-NPCM845-i3c-controller/20240802-183617
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20240801071946.43266-3-yschu%40nuvoton.com
patch subject: [PATCH v1 2/2] i3c: master: Add Nuvoton npcm845 i3c master driver
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20240803/202408030639.LBZ5zgGw-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240803/202408030639.LBZ5zgGw-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/202408030639.LBZ5zgGw-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
>> drivers/i3c/master/npcm845-i3c-master.c:655:2: warning: unannotated fall-through between switch labels [-Wimplicit-fallthrough]
655 | default:
| ^
drivers/i3c/master/npcm845-i3c-master.c:655:2: note: insert 'break;' to avoid fall-through
655 | default:
| ^
| break;
>> drivers/i3c/master/npcm845-i3c-master.c:1112:9: warning: use of bitwise '|' with boolean operands [-Wbitwise-instead-of-logical]
1112 | if ((NPCM_I3C_MSTATUS_STATE_IDLE(reg) |
| ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| ||
1113 | NPCM_I3C_MSTATUS_STATE_SLVREQ(reg)) &&
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/i3c/master/npcm845-i3c-master.c:67:42: note: expanded from macro 'NPCM_I3C_MSTATUS_STATE_IDLE'
67 | #define NPCM_I3C_MSTATUS_STATE_IDLE(x) (NPCM_I3C_MSTATUS_STATE(x) == 0)
| ^
drivers/i3c/master/npcm845-i3c-master.c:1112:9: note: cast one or both operands to int to silence this warning
drivers/i3c/master/npcm845-i3c-master.c:67:42: note: expanded from macro 'NPCM_I3C_MSTATUS_STATE_IDLE'
67 | #define NPCM_I3C_MSTATUS_STATE_IDLE(x) (NPCM_I3C_MSTATUS_STATE(x) == 0)
| ^
>> drivers/i3c/master/npcm845-i3c-master.c:2353:12: error: incompatible function pointer types initializing 'void (*)(struct platform_device *)' with an expression of type 'int (struct platform_device *)' [-Wincompatible-function-pointer-types]
2353 | .remove = npcm_i3c_master_remove,
| ^~~~~~~~~~~~~~~~~~~~~~
2 warnings and 1 error generated.
vim +2353 drivers/i3c/master/npcm845-i3c-master.c
2350
2351 static struct platform_driver npcm_i3c_master = {
2352 .probe = npcm_i3c_master_probe,
> 2353 .remove = npcm_i3c_master_remove,
2354 .driver = {
2355 .name = "npcm845-i3c-master",
2356 .of_match_table = npcm_i3c_master_of_match_tbl,
2357 },
2358 };
2359 module_platform_driver(npcm_i3c_master);
2360
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
--
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
next prev parent reply other threads:[~2024-08-02 23:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 7:19 [PATCH v1 0/2] Add Nuvoton NPCM845 i3c master driver Stanley Chu
2024-08-01 7:19 ` [PATCH v1 1/2] dt-bindings: i3c: Add NPCM845 i3c controller Stanley Chu
2024-08-01 14:53 ` Krzysztof Kozlowski
2024-08-01 23:06 ` Alexandre Belloni
2024-08-05 5:37 ` Stanley Chu
2024-08-05 6:04 ` Stanley Chu
2024-08-01 14:57 ` Krzysztof Kozlowski
2024-08-01 7:19 ` [PATCH v1 2/2] i3c: master: Add Nuvoton npcm845 i3c master driver Stanley Chu
2024-08-01 8:42 ` [PATCH " Markus Elfring
2024-08-01 15:02 ` Krzysztof Kozlowski
2024-08-01 9:06 ` Markus Elfring
2024-08-01 15:02 ` [PATCH v1 " Krzysztof Kozlowski
2024-08-05 6:27 ` Stanley Chu
2024-08-02 16:16 ` Frank Li
2024-08-05 7:19 ` Stanley Chu
2024-08-05 15:17 ` Frank Li
2024-08-06 0:47 ` Stanley Chu
2024-08-06 3:08 ` Frank Li
2024-08-02 21:53 ` kernel test robot
2024-08-02 23:25 ` kernel test robot [this message]
2024-08-03 2:12 ` kernel 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=202408030639.LBZ5zgGw-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=cpchiang1@nuvoton.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kwliu@nuvoton.com \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=openbmc@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=stanley.chuys@gmail.com \
--cc=tomer.maimon@nuvoton.com \
--cc=yschu@nuvoton.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