From: kernel test robot <lkp@intel.com>
To: aspeedyh <yh_chung@aspeedtech.com>,
jk@codeconstruct.com.au, matt@codeconstruct.com.au,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, bmc-sw@aspeedtech.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] net: mctp: Add MCTP PCIe VDM transport driver
Date: Thu, 17 Jul 2025 18:39:15 +0800 [thread overview]
Message-ID: <202507171855.3WJVpX2l-lkp@intel.com> (raw)
In-Reply-To: <20250714062544.2612693-1-yh_chung@aspeedtech.com>
Hi aspeedyh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
[also build test WARNING on net/main linus/master v6.16-rc6 next-20250716]
[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/aspeedyh/net-mctp-Add-MCTP-PCIe-VDM-transport-driver/20250714-142656
base: net-next/main
patch link: https://lore.kernel.org/r/20250714062544.2612693-1-yh_chung%40aspeedtech.com
patch subject: [PATCH] net: mctp: Add MCTP PCIe VDM transport driver
config: powerpc64-randconfig-r122-20250717 (https://download.01.org/0day-ci/archive/20250717/202507171855.3WJVpX2l-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 16534d19bf50bde879a83f0ae62875e2c5120e64)
reproduce: (https://download.01.org/0day-ci/archive/20250717/202507171855.3WJVpX2l-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/202507171855.3WJVpX2l-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/net/mctp/mctp-pcie-vdm.c:130:1: sparse: sparse: symbol 'mctp_pcie_vdm_dev_mutex' was not declared. Should it be static?
>> drivers/net/mctp/mctp-pcie-vdm.c:131:1: sparse: sparse: symbol 'mctp_pcie_vdm_devs' was not declared. Should it be static?
>> drivers/net/mctp/mctp-pcie-vdm.c:132:25: sparse: sparse: symbol 'mctp_pcie_vdm_wq' was not declared. Should it be static?
>> drivers/net/mctp/mctp-pcie-vdm.c:343:9: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [usertype] @@ got restricted __be32 [usertype] @@
drivers/net/mctp/mctp-pcie-vdm.c:343:9: sparse: expected unsigned int [usertype]
drivers/net/mctp/mctp-pcie-vdm.c:343:9: sparse: got restricted __be32 [usertype]
>> drivers/net/mctp/mctp-pcie-vdm.c:398:17: sparse: sparse: cast to restricted __be32
>> drivers/net/mctp/mctp-pcie-vdm.c:398:17: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [usertype] @@ got restricted __le32 [usertype] @@
drivers/net/mctp/mctp-pcie-vdm.c:398:17: sparse: expected unsigned int [usertype]
drivers/net/mctp/mctp-pcie-vdm.c:398:17: sparse: got restricted __le32 [usertype]
drivers/net/mctp/mctp-pcie-vdm.c:453:25: sparse: sparse: cast to restricted __be32
drivers/net/mctp/mctp-pcie-vdm.c:453:25: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [usertype] @@ got restricted __le32 [usertype] @@
drivers/net/mctp/mctp-pcie-vdm.c:453:25: sparse: expected unsigned int [usertype]
drivers/net/mctp/mctp-pcie-vdm.c:453:25: sparse: got restricted __le32 [usertype]
vim +/mctp_pcie_vdm_dev_mutex +130 drivers/net/mctp/mctp-pcie-vdm.c
128
129 /* mutex for vdm_devs add/delete */
> 130 DEFINE_MUTEX(mctp_pcie_vdm_dev_mutex);
> 131 LIST_HEAD(mctp_pcie_vdm_devs);
> 132 struct workqueue_struct *mctp_pcie_vdm_wq;
133
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-07-17 10:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 6:25 aspeedyh
2025-07-14 8:54 ` Jeremy Kerr
2025-07-14 12:37 ` YH Chung
2025-07-15 1:08 ` Jeremy Kerr
2025-07-17 3:07 ` YH Chung
2025-07-17 5:37 ` Jeremy Kerr
2025-07-17 7:17 ` YH Chung
2025-07-17 7:31 ` Jeremy Kerr
2025-07-17 8:21 ` YH Chung
2025-07-17 21:40 ` Adam Young
2025-07-18 3:24 ` Jeremy Kerr
2025-07-17 21:43 ` Adam Young
2025-07-18 5:48 ` Khang D Nguyen
2025-07-18 6:03 ` Jeremy Kerr
2025-07-18 11:05 ` YH Chung
2025-07-15 2:26 ` kernel test robot
2025-07-17 10:39 ` 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=202507171855.3WJVpX2l-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=bmc-sw@aspeedtech.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=yh_chung@aspeedtech.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®