linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Yehuda Yitschak <yehuday@amazon.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Yonatan Nachum <ynachum@amazon.com>,
	Michael Margolin <mrgolin@amazon.com>
Subject: [linux-next:master 5282/8795] drivers/infiniband/hw/efa/efa_main.c:444:30: sparse: sparse: incorrect type in assignment (different base types)
Date: Tue, 3 Sep 2024 21:21:17 +0800	[thread overview]
Message-ID: <202409032113.bvyVfsNp-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   6804f0edbe7747774e6ae60f20cec4ee3ad7c187
commit: 04e36fd27a2aebb03ef019debc4df247f2a427c6 [5282/8795] RDMA/efa: Add support for node guid
config: loongarch-randconfig-r132-20240903 (https://download.01.org/0day-ci/archive/20240903/202409032113.bvyVfsNp-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.1.0
reproduce: (https://download.01.org/0day-ci/archive/20240903/202409032113.bvyVfsNp-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/202409032113.bvyVfsNp-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> drivers/infiniband/hw/efa/efa_main.c:444:30: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted __be64 [usertype] node_guid @@     got unsigned long long [usertype] guid @@
   drivers/infiniband/hw/efa/efa_main.c:444:30: sparse:     expected restricted __be64 [usertype] node_guid
   drivers/infiniband/hw/efa/efa_main.c:444:30: sparse:     got unsigned long long [usertype] guid

vim +444 drivers/infiniband/hw/efa/efa_main.c

   408	
   409	static int efa_ib_device_add(struct efa_dev *dev)
   410	{
   411		struct efa_com_get_hw_hints_result hw_hints;
   412		struct pci_dev *pdev = dev->pdev;
   413		int err;
   414	
   415		efa_stats_init(dev);
   416	
   417		err = efa_com_get_device_attr(&dev->edev, &dev->dev_attr);
   418		if (err)
   419			return err;
   420	
   421		dev_dbg(&dev->pdev->dev, "Doorbells bar (%d)\n", dev->dev_attr.db_bar);
   422		err = efa_request_doorbell_bar(dev);
   423		if (err)
   424			return err;
   425	
   426		err = efa_com_get_hw_hints(&dev->edev, &hw_hints);
   427		if (err)
   428			goto err_release_doorbell_bar;
   429	
   430		efa_update_hw_hints(dev, &hw_hints);
   431	
   432		/* Try to enable all the available aenq groups */
   433		err = efa_com_set_aenq_config(&dev->edev, EFA_AENQ_ENABLED_GROUPS);
   434		if (err)
   435			goto err_release_doorbell_bar;
   436	
   437		err = efa_create_eqs(dev);
   438		if (err)
   439			goto err_release_doorbell_bar;
   440	
   441		efa_set_host_info(dev);
   442	
   443		dev->ibdev.node_type = RDMA_NODE_UNSPECIFIED;
 > 444		dev->ibdev.node_guid = dev->dev_attr.guid;
   445		dev->ibdev.phys_port_cnt = 1;
   446		dev->ibdev.num_comp_vectors = dev->neqs ?: 1;
   447		dev->ibdev.dev.parent = &pdev->dev;
   448	
   449		ib_set_device_ops(&dev->ibdev, &efa_dev_ops);
   450	
   451		dev->ibdev.driver_def = efa_uapi_defs;
   452	
   453		err = ib_register_device(&dev->ibdev, "efa_%d", &pdev->dev);
   454		if (err)
   455			goto err_destroy_eqs;
   456	
   457		ibdev_info(&dev->ibdev, "IB device registered\n");
   458	
   459		return 0;
   460	
   461	err_destroy_eqs:
   462		efa_destroy_eqs(dev);
   463	err_release_doorbell_bar:
   464		efa_release_doorbell_bar(dev);
   465		return err;
   466	}
   467	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


                 reply	other threads:[~2024-09-03 13:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202409032113.bvyVfsNp-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-mm@kvack.org \
    --cc=mrgolin@amazon.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yehuday@amazon.com \
    --cc=ynachum@amazon.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