From: kernel test robot <lkp@intel.com>
To: admiyo@os.amperecomputing.com,
Jeremy Kerr <jk@codeconstruct.com.au>,
Matt Johnston <matt@codeconstruct.com.au>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Sudeep Holla <sudeep.holla@arm.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Huisong Li <lihuisong@huawei.com>
Subject: Re: [PATCH net-next v25 1/1] mctp pcc: Implement MCTP over PCC Transport
Date: Thu, 28 Aug 2025 01:54:48 +0800 [thread overview]
Message-ID: <202508280145.bix2s4fv-lkp@intel.com> (raw)
In-Reply-To: <20250827044810.152775-2-admiyo@os.amperecomputing.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/admiyo-os-amperecomputing-com/mctp-pcc-Implement-MCTP-over-PCC-Transport/20250827-124953
base: net-next/main
patch link: https://lore.kernel.org/r/20250827044810.152775-2-admiyo%40os.amperecomputing.com
patch subject: [PATCH net-next v25 1/1] mctp pcc: Implement MCTP over PCC Transport
config: i386-randconfig-002-20250827 (https://download.01.org/0day-ci/archive/20250828/202508280145.bix2s4fv-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250828/202508280145.bix2s4fv-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/202508280145.bix2s4fv-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/mctp/mctp-pcc.c:110:24: warning: variable 'mctp_pcc_ndev' set but not used [-Wunused-but-set-variable]
110 | struct mctp_pcc_ndev *mctp_pcc_ndev;
| ^
1 warning generated.
vim +/mctp_pcc_ndev +110 drivers/net/mctp/mctp-pcc.c
107
108 static void mctp_pcc_tx_done(struct mbox_client *c, void *mssg, int r)
109 {
> 110 struct mctp_pcc_ndev *mctp_pcc_ndev;
111 struct mctp_pcc_mailbox *box;
112 struct sk_buff *skb = NULL;
113 struct sk_buff *curr_skb;
114
115 mctp_pcc_ndev = container_of(c, struct mctp_pcc_ndev, outbox.client);
116 box = container_of(c, struct mctp_pcc_mailbox, client);
117 spin_lock(&box->packets.lock);
118 skb_queue_walk(&box->packets, curr_skb) {
119 skb = curr_skb;
120 if (skb->data == mssg) {
121 __skb_unlink(skb, &box->packets);
122 break;
123 }
124 }
125 spin_unlock(&box->packets.lock);
126
127 if (skb)
128 dev_consume_skb_any(skb);
129 }
130
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-27 17:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 4:48 [PATCH net-next v25 0/1] MCTP Over PCC Transport admiyo
2025-08-27 4:48 ` [PATCH net-next v25 1/1] mctp pcc: Implement MCTP over " admiyo
2025-08-27 7:36 ` Jeremy Kerr
2025-08-27 17:54 ` kernel test robot [this message]
2025-08-29 9:17 ` kernel test robot
2025-08-29 19:32 ` ALOK TIWARI
2025-09-01 0:59 ` Jeremy Kerr
2025-09-05 17:25 ` Adam Young
2025-08-27 4:57 ` [PATCH net-next v25 0/1] MCTP Over " Adam Young
-- strict thread matches above, loose matches on Subject: below --
2025-08-19 20:51 admiyo
2025-08-19 20:51 ` [PATCH net-next v25 1/1] mctp pcc: Implement MCTP over " admiyo
2025-08-22 8:21 ` Jeremy Kerr
2025-08-26 20:51 ` Adam Young
2025-08-27 1:37 ` Jeremy Kerr
2025-08-27 4:55 ` Adam Young
2025-08-26 22:37 ` Adam Young
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=202508280145.bix2s4fv-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=admiyo@os.amperecomputing.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=lihuisong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=sudeep.holla@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 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.