From: kernel test robot <lkp@intel.com>
To: Hamish Martin <hamish.martin@alliedtelesis.co.nz>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: drivers/uio/uio.c:520:21: sparse: sparse: incorrect type in assignment (different base types)
Date: Sun, 11 Feb 2024 10:03:12 +0800 [thread overview]
Message-ID: <202402111048.4XHz0rkp-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: a5b6244cf87c50358f5562b8f07f7ac35fc7f6b0
commit: a93e7b331568227500186a465fee3c2cb5dffd1f uio: Prevent device destruction while fds are open
date: 6 years ago
config: x86_64-randconfig-x051-20230705 (https://download.01.org/0day-ci/archive/20240211/202402111048.4XHz0rkp-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240211/202402111048.4XHz0rkp-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/202402111048.4XHz0rkp-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/uio/uio.c:520:21: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __poll_t [usertype] ret @@ got int @@
drivers/uio/uio.c:520:21: sparse: expected restricted __poll_t [usertype] ret
drivers/uio/uio.c:520:21: sparse: got int
drivers/uio/uio.c:852: warning: expecting prototype for uio_register_device(). Prototype was for __uio_register_device() instead
vim +520 drivers/uio/uio.c
510
511 static __poll_t uio_poll(struct file *filep, poll_table *wait)
512 {
513 struct uio_listener *listener = filep->private_data;
514 struct uio_device *idev = listener->dev;
515 __poll_t ret = 0;
516 unsigned long flags;
517
518 spin_lock_irqsave(&idev->info_lock, flags);
519 if (!idev->info || !idev->info->irq)
> 520 ret = -EIO;
521 spin_unlock_irqrestore(&idev->info_lock, flags);
522
523 if (ret)
524 return ret;
525
526 poll_wait(filep, &idev->wait, wait);
527 if (listener->event_count != atomic_read(&idev->event))
528 return EPOLLIN | EPOLLRDNORM;
529 return 0;
530 }
531
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-11 2:03 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=202402111048.4XHz0rkp-lkp@intel.com \
--to=lkp@intel.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=hamish.martin@alliedtelesis.co.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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®