From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android12-5.10 0/1] kernel/trace/ring_buffer.c:813: warning: Function parameter or member 'cpu' not described in 'ring_buffer_wake_waiters'
Date: Sat, 04 Jul 2026 16:29:54 +0800 [thread overview]
Message-ID: <202607041625.AsllUH9a-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android12-5.10
head: a00af2707c1d0a67daa8f91db74300f65d84db3b
commit: 588f02f8b9d96c4a89db955394ec54e77b1d482f [0/1] ring-buffer: Add ring_buffer_wake_waiters()
config: i386-randconfig-012-20260702 (https://download.01.org/0day-ci/archive/20260704/202607041625.AsllUH9a-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260704/202607041625.AsllUH9a-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/202607041625.AsllUH9a-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/trace/ring_buffer.c:813: warning: Function parameter or member 'cpu' not described in 'ring_buffer_wake_waiters'
kernel/trace/ring_buffer.c:1424: warning: Function parameter or member 'cpu_buffer' not described in 'rb_check_list'
kernel/trace/ring_buffer.c:1424: warning: Function parameter or member 'list' not described in 'rb_check_list'
kernel/trace/ring_buffer.c:5005: warning: Excess function parameter 'cpu' description in 'ring_buffer_reset_online_cpus'
vim +813 kernel/trace/ring_buffer.c
804
805 /**
806 * ring_buffer_wake_waiters - wake up any waiters on this ring buffer
807 * @buffer: The ring buffer to wake waiters on
808 *
809 * In the case of a file that represents a ring buffer is closing,
810 * it is prudent to wake up any waiters that are on this.
811 */
812 void ring_buffer_wake_waiters(struct trace_buffer *buffer, int cpu)
> 813 {
814 struct ring_buffer_per_cpu *cpu_buffer;
815 struct rb_irq_work *rbwork;
816
817 if (cpu == RING_BUFFER_ALL_CPUS) {
818
819 /* Wake up individual ones too. One level recursion */
820 for_each_buffer_cpu(buffer, cpu)
821 ring_buffer_wake_waiters(buffer, cpu);
822
823 rbwork = &buffer->irq_work;
824 } else {
825 cpu_buffer = buffer->buffers[cpu];
826 rbwork = &cpu_buffer->irq_work;
827 }
828
829 rbwork->wait_index++;
830 /* make sure the waiters see the new index */
831 smp_wmb();
832
833 rb_wake_up_waiters(&rbwork->work);
834 }
835
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-04 8:30 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=202607041625.AsllUH9a-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.