From: kernel test robot <lkp@intel.com>
To: Aman Kumar Pandey <aman.kumarpandey@nxp.com>,
linux-kernel@vger.kernel.org, linux-i3c@lists.infradead.org,
alexandre.belloni@bootlin.com, krzk+dt@kernel.org,
robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, vikash.bansal@nxp.com,
priyanka.jain@nxp.com, shashank.rebbapragada@nxp.com,
Frank.Li@nxp.com, Aman Kumar Pandey <aman.kumarpandey@nxp.com>
Subject: Re: [PATCH 2/2] drivers: i3c: Add driver for NXP P3H2x4x i3c-hub device
Date: Fri, 14 Feb 2025 12:21:13 +0800 [thread overview]
Message-ID: <202502141155.osJiWAHL-lkp@intel.com> (raw)
In-Reply-To: <20250212132227.1348374-2-aman.kumarpandey@nxp.com>
Hi Aman,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on linus/master v6.14-rc2 next-20250213]
[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/Aman-Kumar-Pandey/drivers-i3c-Add-driver-for-NXP-P3H2x4x-i3c-hub-device/20250212-213659
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20250212132227.1348374-2-aman.kumarpandey%40nxp.com
patch subject: [PATCH 2/2] drivers: i3c: Add driver for NXP P3H2x4x i3c-hub device
config: i386-randconfig-r111-20250214 (https://download.01.org/0day-ci/archive/20250214/202502141155.osJiWAHL-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250214/202502141155.osJiWAHL-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/202502141155.osJiWAHL-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/i3c/p3h2x4x/p3h2x4x_i3c_hub_common.c:9:22: sparse: sparse: symbol 'p3h2x4x_ibireq' was not declared. Should it be static?
>> drivers/i3c/p3h2x4x/p3h2x4x_i3c_hub_common.c:15:22: sparse: sparse: symbol 'p3h2x4x_regmap_config' was not declared. Should it be static?
>> drivers/i3c/p3h2x4x/p3h2x4x_i3c_hub_common.c:37:26: sparse: sparse: Using plain integer as NULL pointer
drivers/i3c/p3h2x4x/p3h2x4x_i3c_hub_common.c: note: in included file (through include/linux/module.h, drivers/i3c/p3h2x4x/p3h2x4x_i3c_hub.h):
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
vim +/p3h2x4x_ibireq +9 drivers/i3c/p3h2x4x/p3h2x4x_i3c_hub_common.c
8
> 9 struct i3c_ibi_setup p3h2x4x_ibireq = {
10 .handler = p3h2x4x_ibi_handler,
11 .max_payload_len = P3H2x4x_MAX_PAYLOAD_LEN,
12 .num_slots = P3H2x4x_NUM_SLOTS,
13 };
14
> 15 struct regmap_config p3h2x4x_regmap_config = {
16 .reg_bits = P3H2x4x_REG_BITS,
17 .val_bits = P3H2x4x_VAL_BITS,
18 };
19
20 /* p3h2x4x ids (i3c) */
21 static const struct i3c_device_id p3h2x4x_i3c_ids[] = {
22 I3C_CLASS(I3C_DCR_HUB, NULL),
23 { /* sentinel */ },
24 };
25 MODULE_DEVICE_TABLE(i3c, p3h2x4x_i3c_ids);
26
27 /* p3h2x4x ids (i2c) */
28 static const struct i2c_device_id p3h2x4x_i2c_id_table[] = {
29 { "nxp-i3c-hub", P3H2x4x_HUB_ID },
30 { /* sentinel */ },
31 };
32 MODULE_DEVICE_TABLE(i2c, p3h2x4x_i2c_id_table);
33
34 static const struct of_device_id p3h2x4x_i2c_of_match[] = {
35 {
36 .compatible = "nxp,p3h2x4x",
> 37 .data = P3H2x4x_HUB_ID,
38 },
39 { /* sentinel */ },
40 };
41 MODULE_DEVICE_TABLE(of, p3h2x4x_i2c_of_match);
42
--
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
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Aman Kumar Pandey <aman.kumarpandey@nxp.com>,
linux-kernel@vger.kernel.org, linux-i3c@lists.infradead.org,
alexandre.belloni@bootlin.com, krzk+dt@kernel.org,
robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, vikash.bansal@nxp.com,
priyanka.jain@nxp.com, shashank.rebbapragada@nxp.com,
Frank.Li@nxp.com, Aman Kumar Pandey <aman.kumarpandey@nxp.com>
Subject: Re: [PATCH 2/2] drivers: i3c: Add driver for NXP P3H2x4x i3c-hub device
Date: Fri, 14 Feb 2025 12:21:13 +0800 [thread overview]
Message-ID: <202502141155.osJiWAHL-lkp@intel.com> (raw)
In-Reply-To: <20250212132227.1348374-2-aman.kumarpandey@nxp.com>
Hi Aman,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on linus/master v6.14-rc2 next-20250213]
[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/Aman-Kumar-Pandey/drivers-i3c-Add-driver-for-NXP-P3H2x4x-i3c-hub-device/20250212-213659
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20250212132227.1348374-2-aman.kumarpandey%40nxp.com
patch subject: [PATCH 2/2] drivers: i3c: Add driver for NXP P3H2x4x i3c-hub device
config: i386-randconfig-r111-20250214 (https://download.01.org/0day-ci/archive/20250214/202502141155.osJiWAHL-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250214/202502141155.osJiWAHL-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/202502141155.osJiWAHL-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/i3c/p3h2x4x/p3h2x4x_i3c_hub_common.c:9:22: sparse: sparse: symbol 'p3h2x4x_ibireq' was not declared. Should it be static?
>> drivers/i3c/p3h2x4x/p3h2x4x_i3c_hub_common.c:15:22: sparse: sparse: symbol 'p3h2x4x_regmap_config' was not declared. Should it be static?
>> drivers/i3c/p3h2x4x/p3h2x4x_i3c_hub_common.c:37:26: sparse: sparse: Using plain integer as NULL pointer
drivers/i3c/p3h2x4x/p3h2x4x_i3c_hub_common.c: note: in included file (through include/linux/module.h, drivers/i3c/p3h2x4x/p3h2x4x_i3c_hub.h):
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
vim +/p3h2x4x_ibireq +9 drivers/i3c/p3h2x4x/p3h2x4x_i3c_hub_common.c
8
> 9 struct i3c_ibi_setup p3h2x4x_ibireq = {
10 .handler = p3h2x4x_ibi_handler,
11 .max_payload_len = P3H2x4x_MAX_PAYLOAD_LEN,
12 .num_slots = P3H2x4x_NUM_SLOTS,
13 };
14
> 15 struct regmap_config p3h2x4x_regmap_config = {
16 .reg_bits = P3H2x4x_REG_BITS,
17 .val_bits = P3H2x4x_VAL_BITS,
18 };
19
20 /* p3h2x4x ids (i3c) */
21 static const struct i3c_device_id p3h2x4x_i3c_ids[] = {
22 I3C_CLASS(I3C_DCR_HUB, NULL),
23 { /* sentinel */ },
24 };
25 MODULE_DEVICE_TABLE(i3c, p3h2x4x_i3c_ids);
26
27 /* p3h2x4x ids (i2c) */
28 static const struct i2c_device_id p3h2x4x_i2c_id_table[] = {
29 { "nxp-i3c-hub", P3H2x4x_HUB_ID },
30 { /* sentinel */ },
31 };
32 MODULE_DEVICE_TABLE(i2c, p3h2x4x_i2c_id_table);
33
34 static const struct of_device_id p3h2x4x_i2c_of_match[] = {
35 {
36 .compatible = "nxp,p3h2x4x",
> 37 .data = P3H2x4x_HUB_ID,
38 },
39 { /* sentinel */ },
40 };
41 MODULE_DEVICE_TABLE(of, p3h2x4x_i2c_of_match);
42
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-02-14 4:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 13:22 [PATCH 1/2] dt-bindings: i3c: Add NXP P3H2x4x i3c-hub support Aman Kumar Pandey
2025-02-12 13:22 ` Aman Kumar Pandey
2025-02-12 13:22 ` [PATCH 2/2] drivers: i3c: Add driver for NXP P3H2x4x i3c-hub device Aman Kumar Pandey
2025-02-12 13:22 ` Aman Kumar Pandey
2025-02-12 16:42 ` Frank Li
2025-02-12 16:42 ` Frank Li
2025-02-12 16:53 ` Krzysztof Kozlowski
2025-02-12 16:53 ` Krzysztof Kozlowski
2025-02-12 18:20 ` Alexandre Belloni
2025-02-12 18:20 ` Alexandre Belloni
2025-02-13 11:49 ` kernel test robot
2025-02-13 11:49 ` kernel test robot
2025-02-13 17:46 ` kernel test robot
2025-02-13 17:46 ` kernel test robot
2025-02-14 4:21 ` kernel test robot [this message]
2025-02-14 4:21 ` kernel test robot
2025-02-16 15:17 ` Dan Carpenter
2025-02-16 15:17 ` Dan Carpenter
2025-02-19 4:52 ` kernel test robot
2025-02-19 4:52 ` kernel test robot
2025-02-12 15:25 ` [PATCH 1/2] dt-bindings: i3c: Add NXP P3H2x4x i3c-hub support Rob Herring (Arm)
2025-02-12 15:25 ` Rob Herring (Arm)
2025-02-12 16:23 ` Frank Li
2025-02-12 16:23 ` Frank Li
2025-02-12 16:49 ` Krzysztof Kozlowski
2025-02-12 16:49 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2025-02-15 1:02 [PATCH 2/2] drivers: i3c: Add driver for NXP P3H2x4x i3c-hub device 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=202502141155.osJiWAHL-lkp@intel.com \
--to=lkp@intel.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=aman.kumarpandey@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=priyanka.jain@nxp.com \
--cc=robh@kernel.org \
--cc=shashank.rebbapragada@nxp.com \
--cc=vikash.bansal@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.