From: kernel test robot <lkp@intel.com>
To: Justin Lai <justinlai0215@realtek.com>, kuba@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
andrew@lunn.ch, pkshih@realtek.com, larry.chiu@realtek.com,
Justin Lai <justinlai0215@realtek.com>
Subject: Re: [PATCH net-next v9 12/13] net:ethernet:realtek: Update the Makefile and Kconfig in the realtek folder
Date: Thu, 5 Oct 2023 07:47:49 +0800 [thread overview]
Message-ID: <202310050703.fr8Txbrs-lkp@intel.com> (raw)
In-Reply-To: <20230928104920.113511-13-justinlai0215@realtek.com>
Hi Justin,
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/Justin-Lai/net-ethernet-realtek-rtase-Add-pci-table-supported-in-this-module/20230928-185229
base: net-next/main
patch link: https://lore.kernel.org/r/20230928104920.113511-13-justinlai0215%40realtek.com
patch subject: [PATCH net-next v9 12/13] net:ethernet:realtek: Update the Makefile and Kconfig in the realtek folder
config: i386-randconfig-061-20231005 (https://download.01.org/0day-ci/archive/20231005/202310050703.fr8Txbrs-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/20231005/202310050703.fr8Txbrs-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/202310050703.fr8Txbrs-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/net/ethernet/realtek/rtase/rtase_main.c:203:20: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le64 [usertype] addr @@ got long long @@
drivers/net/ethernet/realtek/rtase/rtase_main.c:203:20: sparse: expected restricted __le64 [usertype] addr
drivers/net/ethernet/realtek/rtase/rtase_main.c:203:20: sparse: got long long
drivers/net/ethernet/realtek/rtase/rtase_main.c:362:29: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le64 [usertype] addr @@ got long long @@
drivers/net/ethernet/realtek/rtase/rtase_main.c:362:29: sparse: expected restricted __le64 [usertype] addr
drivers/net/ethernet/realtek/rtase/rtase_main.c:362:29: sparse: got long long
>> drivers/net/ethernet/realtek/rtase/rtase_main.c:686:37: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:687:37: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:692:19: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:694:37: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:708:27: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:710:27: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:727:35: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:729:35: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:732:35: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:734:35: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:1580:19: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:1584:37: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:1614:29: sparse: sparse: cast to restricted __le64
>> drivers/net/ethernet/realtek/rtase/rtase_main.c:1614:29: sparse: sparse: cast from restricted __le32
drivers/net/ethernet/realtek/rtase/rtase_main.c:1615:36: sparse: sparse: cast to restricted __le64
>> drivers/net/ethernet/realtek/rtase/rtase_main.c:1615:36: sparse: sparse: cast from restricted __le16
drivers/net/ethernet/realtek/rtase/rtase_main.c:1616:35: sparse: sparse: cast to restricted __le64
drivers/net/ethernet/realtek/rtase/rtase_main.c:1616:35: sparse: sparse: cast from restricted __le16
vim +203 drivers/net/ethernet/realtek/rtase/rtase_main.c
1f431ee317f33f Justin Lai 2023-09-28 195
29576bc3be86aa Justin Lai 2023-09-28 196 static void rtase_unmap_tx_skb(struct pci_dev *pdev, u32 len,
29576bc3be86aa Justin Lai 2023-09-28 197 struct tx_desc *desc)
29576bc3be86aa Justin Lai 2023-09-28 198 {
29576bc3be86aa Justin Lai 2023-09-28 199 dma_unmap_single(&pdev->dev, le64_to_cpu(desc->addr), len,
29576bc3be86aa Justin Lai 2023-09-28 200 DMA_TO_DEVICE);
29576bc3be86aa Justin Lai 2023-09-28 201 desc->opts1 = cpu_to_le32(RTK_OPTS1_DEBUG_VALUE);
29576bc3be86aa Justin Lai 2023-09-28 202 desc->opts2 = 0x00;
29576bc3be86aa Justin Lai 2023-09-28 @203 desc->addr = RTK_MAGIC_NUMBER;
29576bc3be86aa Justin Lai 2023-09-28 204 }
29576bc3be86aa Justin Lai 2023-09-28 205
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-04 23:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 10:49 [PATCH net-next v9 00/13] Add Realtek automotive PCIe driver Justin Lai
2023-09-28 10:49 ` [PATCH net-next v9 01/13] net:ethernet:realtek:rtase: Add pci table supported in this module Justin Lai
2023-09-28 10:49 ` [PATCH net-next v9 02/13] net:ethernet:realtek:rtase: Implement the .ndo_open function Justin Lai
2023-09-28 12:57 ` Andrew Lunn
2023-10-03 12:40 ` Justin Lai
2023-09-28 10:49 ` [PATCH net-next v9 03/13] net:ethernet:realtek:rtase: Implement the rtase_down function Justin Lai
2023-09-28 10:49 ` [PATCH net-next v9 04/13] net:ethernet:realtek:rtase: Implement the interrupt routine and rtase_poll Justin Lai
2023-09-28 10:49 ` [PATCH net-next v9 05/13] net:ethernet:realtek:rtase: Implement hardware configuration function Justin Lai
2023-09-28 10:49 ` [PATCH net-next v9 06/13] net:ethernet:realtek:rtase: Implement .ndo_start_xmit function Justin Lai
2023-09-28 10:49 ` [PATCH net-next v9 07/13] net:ethernet:realtek:rtase: Implement a function to receive packets Justin Lai
2023-09-28 10:49 ` [PATCH net-next v9 08/13] net:ethernet:realtek:rtase: Implement net_device_ops Justin Lai
2023-09-28 14:02 ` Andrew Lunn
2023-10-06 4:02 ` Justin Lai
2023-10-06 13:44 ` Andrew Lunn
2023-10-16 1:49 ` Justin Lai
2023-09-28 10:49 ` [PATCH net-next v9 09/13] net:ethernet:realtek:rtase: Implement pci_driver suspend and resume function Justin Lai
2023-09-28 10:49 ` [PATCH net-next v9 10/13] net:ethernet:realtek:rtase: Implement ethtool function Justin Lai
2023-09-28 10:49 ` [PATCH net-next v9 11/13] net:ethernet:realtek:rtase: Add a Makefile in the rtase folder Justin Lai
2023-09-28 10:49 ` [PATCH net-next v9 12/13] net:ethernet:realtek: Update the Makefile and Kconfig in the realtek folder Justin Lai
2023-09-28 21:00 ` kernel test robot
2023-10-04 23:47 ` kernel test robot [this message]
2023-09-28 10:49 ` [PATCH net-next v9 13/13] MAINTAINERS: Add the rtase ethernet driver entry Justin Lai
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=202310050703.fr8Txbrs-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=justinlai0215@realtek.com \
--cc=kuba@kernel.org \
--cc=larry.chiu@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=pkshih@realtek.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;
as well as URLs for NNTP newsgroup(s).