All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android12-kiwi-5.10 150/150] kernel/events/ring_buffer.c:22:9: sparse: sparse: incorrect type in assignment (different base types)
Date: Mon, 1 Sep 2025 12:26:52 +0800	[thread overview]
Message-ID: <202509011229.F49FqqMo-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android12-kiwi-5.10
head:   77354ed8fe97f2e66ce08870a5cd54e222a15c53
commit: ef0398cf5cf150364839ffea0b0dd7c71edf2e62 [150/150] perf/ring_buffer: Allow the EPOLLRDNORM flag for poll
config: arm-randconfig-r133-20250727 (https://download.01.org/0day-ci/archive/20250901/202509011229.F49FqqMo-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
reproduce: (https://download.01.org/0day-ci/archive/20250901/202509011229.F49FqqMo-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/202509011229.F49FqqMo-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> kernel/events/ring_buffer.c:22:9: sparse: sparse: incorrect type in assignment (different base types) @@     expected int volatile @@     got restricted __poll_t @@
   kernel/events/ring_buffer.c:22:9: sparse:     expected int volatile
   kernel/events/ring_buffer.c:22:9: sparse:     got restricted __poll_t
   kernel/events/ring_buffer.c:170:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/ring_buffer.c:170:14: sparse:    struct perf_buffer [noderef] __rcu *
   kernel/events/ring_buffer.c:170:14: sparse:    struct perf_buffer *
   kernel/events/ring_buffer.c:170:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/ring_buffer.c:170:14: sparse:    struct perf_buffer [noderef] __rcu *
   kernel/events/ring_buffer.c:170:14: sparse:    struct perf_buffer *
   kernel/events/ring_buffer.c:170:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
   kernel/events/ring_buffer.c:170:14: sparse:    struct perf_buffer [noderef] __rcu *
   kernel/events/ring_buffer.c:170:14: sparse:    struct perf_buffer *

vim +22 kernel/events/ring_buffer.c

    19	
    20	static void perf_output_wakeup(struct perf_output_handle *handle)
    21	{
  > 22		atomic_set(&handle->rb->poll, EPOLLIN | EPOLLRDNORM);
    23	
    24		handle->event->pending_wakeup = 1;
    25		irq_work_queue(&handle->event->pending);
    26	}
    27	

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

             reply	other threads:[~2025-09-01  4:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01  4:26 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-09 15:43 [android-common:android12-kiwi-5.10 150/150] kernel/events/ring_buffer.c:22:9: sparse: sparse: incorrect type in assignment (different base types) kernel test robot
2025-07-27  3:01 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=202509011229.F49FqqMo-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.