From: kernel test robot <yujie.liu@intel.com>
To: Shinas Rasheed <srasheed@marvell.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <oe-kbuild-all@lists.linux.dev>, <hgani@marvell.com>,
<vimleshk@marvell.com>, <egallen@redhat.com>,
<mschmidt@redhat.com>, <pabeni@redhat.com>, <horms@kernel.org>,
<kuba@kernel.org>, <davem@davemloft.net>, <wizhao@redhat.com>,
<kheib@redhat.com>, <konguyen@redhat.com>,
Shinas Rasheed <srasheed@marvell.com>,
"Veerasenareddy Burru" <vburru@marvell.com>,
Sathesh Edara <sedara@marvell.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next v1 1/4] octeon_ep: add PF-VF mailbox communication
Date: Mon, 11 Dec 2023 08:54:46 +0800 [thread overview]
Message-ID: <202312100726.wnsqAU5W-lkp@intel.com> (raw)
In-Reply-To: <20231208070352.2606192-2-srasheed@marvell.com>
Hi Shinas,
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/Shinas-Rasheed/octeon_ep-add-PF-VF-mailbox-communication/20231208-150756
base: net-next/main
patch link: https://lore.kernel.org/r/20231208070352.2606192-2-srasheed%40marvell.com
patch subject: [PATCH net-next v1 1/4] octeon_ep: add PF-VF mailbox communication
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231210/202312100726.wnsqAU5W-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 <yujie.liu@intel.com>
| Closes: https://lore.kernel.org/r/202312100726.wnsqAU5W-lkp@intel.com/
includecheck warnings: (new ones prefixed by >>)
>> drivers/net/ethernet/marvell/octeon_ep/octep_pfvf_mbox.c: linux/types.h is included more than once.
vim +8 drivers/net/ethernet/marvell/octeon_ep/octep_pfvf_mbox.c
> 8 #include <linux/types.h>
> 9 #include <linux/types.h>
10 #include <linux/errno.h>
11 #include <linux/string.h>
12 #include <linux/mutex.h>
13 #include <linux/jiffies.h>
14 #include <linux/sched.h>
15 #include <linux/sched/signal.h>
16 #include <linux/io.h>
17 #include <linux/pci.h>
18 #include <linux/etherdevice.h>
19
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-11 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 7:03 [PATCH net-next v1 0/4] add PF-VF mailbox support Shinas Rasheed
2023-12-08 7:03 ` [PATCH net-next v1 1/4] octeon_ep: add PF-VF mailbox communication Shinas Rasheed
2023-12-08 17:29 ` kernel test robot
2023-12-11 0:54 ` kernel test robot [this message]
2023-12-08 7:03 ` [PATCH net-next v1 2/4] octeon_ep: PF-VF mailbox version support Shinas Rasheed
2023-12-08 7:03 ` [PATCH net-next v1 3/4] octeon_ep: control net framework to support VF offloads Shinas Rasheed
2023-12-08 7:03 ` [PATCH net-next v1 4/4] octeon_ep: support firmware notifications for VFs Shinas Rasheed
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=202312100726.wnsqAU5W-lkp@intel.com \
--to=yujie.liu@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=egallen@redhat.com \
--cc=hgani@marvell.com \
--cc=horms@kernel.org \
--cc=kheib@redhat.com \
--cc=konguyen@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=sedara@marvell.com \
--cc=srasheed@marvell.com \
--cc=vburru@marvell.com \
--cc=vimleshk@marvell.com \
--cc=wizhao@redhat.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®