From: kernel test robot <lkp@intel.com>
To: admiyo@os.amperecomputing.com,
Sudeep Holla <sudeep.holla@arm.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jeremy Kerr <jk@codeconstruct.com.au>,
Matt Johnston <matt@codeconstruct.com.au>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Huisong Li <lihuisong@huawei.com>
Subject: Re: [PATCH v7 1/2] mctp pcc: Check before sending MCTP PCC response ACK
Date: Sun, 17 Nov 2024 09:06:41 +0800 [thread overview]
Message-ID: <202411170849.DynEPZlM-lkp@intel.com> (raw)
In-Reply-To: <20241114024928.60004-2-admiyo@os.amperecomputing.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on rafael-pm/bleeding-edge linus/master v6.12-rc7 next-20241115]
[cannot apply to horms-ipvs/master]
[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/admiyo-os-amperecomputing-com/mctp-pcc-Check-before-sending-MCTP-PCC-response-ACK/20241114-105151
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20241114024928.60004-2-admiyo%40os.amperecomputing.com
patch subject: [PATCH v7 1/2] mctp pcc: Check before sending MCTP PCC response ACK
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20241117/202411170849.DynEPZlM-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241117/202411170849.DynEPZlM-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/202411170849.DynEPZlM-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/mailbox/pcc.c:115: warning: Excess struct member 'shmem_base_addr' description in 'pcc_chan_info'
vim +115 drivers/mailbox/pcc.c
800cda7b63f22b Sudeep Holla 2021-09-17 82
80b2bdde002c52 Sudeep Holla 2021-09-17 83 /**
80b2bdde002c52 Sudeep Holla 2021-09-17 84 * struct pcc_chan_info - PCC channel specific information
80b2bdde002c52 Sudeep Holla 2021-09-17 85 *
0f2591e21b2e85 Sudeep Holla 2021-09-17 86 * @chan: PCC channel information with Shared Memory Region info
bf18123e78f4d1 Sudeep Holla 2021-09-17 87 * @db: PCC register bundle for the doorbell register
bf18123e78f4d1 Sudeep Holla 2021-09-17 88 * @plat_irq_ack: PCC register bundle for the platform interrupt acknowledge
bf18123e78f4d1 Sudeep Holla 2021-09-17 89 * register
c45ded7e11352d Sudeep Holla 2021-09-17 90 * @cmd_complete: PCC register bundle for the command complete check register
c45ded7e11352d Sudeep Holla 2021-09-17 91 * @cmd_update: PCC register bundle for the command complete update register
c45ded7e11352d Sudeep Holla 2021-09-17 92 * @error: PCC register bundle for the error status register
7cd506129724fe Adam Young 2024-11-13 93 * @shmem_base_addr: the virtual memory address of the shared buffer
f92ae90e52bb09 Sudeep Holla 2021-09-17 94 * @plat_irq: platform interrupt
60c40b06fa6869 Huisong Li 2023-08-01 95 * @type: PCC subspace type
3db174e478cb0b Huisong Li 2023-08-01 96 * @plat_irq_flags: platform interrupt flags
3db174e478cb0b Huisong Li 2023-08-01 97 * @chan_in_use: this flag is used just to check if the interrupt needs
3db174e478cb0b Huisong Li 2023-08-01 98 * handling when it is shared. Since only one transfer can occur
3db174e478cb0b Huisong Li 2023-08-01 99 * at a time and mailbox takes care of locking, this flag can be
3db174e478cb0b Huisong Li 2023-08-01 100 * accessed without a lock. Note: the type only support the
3db174e478cb0b Huisong Li 2023-08-01 101 * communication from OSPM to Platform, like type3, use it, and
3db174e478cb0b Huisong Li 2023-08-01 102 * other types completely ignore it.
80b2bdde002c52 Sudeep Holla 2021-09-17 103 */
80b2bdde002c52 Sudeep Holla 2021-09-17 104 struct pcc_chan_info {
0f2591e21b2e85 Sudeep Holla 2021-09-17 105 struct pcc_mbox_chan chan;
bf18123e78f4d1 Sudeep Holla 2021-09-17 106 struct pcc_chan_reg db;
bf18123e78f4d1 Sudeep Holla 2021-09-17 107 struct pcc_chan_reg plat_irq_ack;
c45ded7e11352d Sudeep Holla 2021-09-17 108 struct pcc_chan_reg cmd_complete;
c45ded7e11352d Sudeep Holla 2021-09-17 109 struct pcc_chan_reg cmd_update;
c45ded7e11352d Sudeep Holla 2021-09-17 110 struct pcc_chan_reg error;
f92ae90e52bb09 Sudeep Holla 2021-09-17 111 int plat_irq;
60c40b06fa6869 Huisong Li 2023-08-01 112 u8 type;
3db174e478cb0b Huisong Li 2023-08-01 113 unsigned int plat_irq_flags;
3db174e478cb0b Huisong Li 2023-08-01 114 bool chan_in_use;
80b2bdde002c52 Sudeep Holla 2021-09-17 @115 };
80b2bdde002c52 Sudeep Holla 2021-09-17 116
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-17 1:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 2:49 [PATCH v7 0/2] MCTP Over PCC Transport admiyo
2024-11-14 2:49 ` [PATCH v7 1/2] mctp pcc: Check before sending MCTP PCC response ACK admiyo
2024-11-17 1:06 ` kernel test robot [this message]
2024-11-17 1:28 ` kernel test robot
2024-11-17 15:39 ` kernel test robot
2024-11-14 2:49 ` [PATCH v7 2/2] mctp pcc: Implement MCTP over PCC Transport admiyo
2024-11-15 7:27 ` Jeremy Kerr
2024-11-17 3:04 ` 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=202411170849.DynEPZlM-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=admiyo@os.amperecomputing.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jassisinghbrar@gmail.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=lenb@kernel.org \
--cc=lihuisong@huawei.com \
--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=rafael@kernel.org \
--cc=robert.moore@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox