From: kernel test robot <lkp@intel.com>
To: Vincent Donnefort <vdonnefort@google.com>,
rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com,
linux-trace-kernel@vger.kernel.org, maz@kernel.org,
oliver.upton@linux.dev, joey.gouly@arm.com,
suzuki.poulose@arm.com, yuzenghui@huawei.com
Cc: oe-kbuild-all@lists.linux.dev, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, jstultz@google.com,
qperret@google.com, will@kernel.org, kernel-team@android.com,
linux-kernel@vger.kernel.org,
Vincent Donnefort <vdonnefort@google.com>
Subject: Re: [PATCH v2 02/12] ring-buffer: Introducing ring-buffer remote
Date: Fri, 10 Jan 2025 00:45:19 +0800 [thread overview]
Message-ID: <202501100025.WNnMyW13-lkp@intel.com> (raw)
In-Reply-To: <20250108114536.627715-3-vdonnefort@google.com>
Hi Vincent,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 09a0fa92e5b45e99cf435b2fbf5ebcf889cf8780]
url: https://github.com/intel-lab-lkp/linux/commits/Vincent-Donnefort/ring-buffer-Check-for-empty-ring-buffer-with-rb_num_of_entries/20250108-200217
base: 09a0fa92e5b45e99cf435b2fbf5ebcf889cf8780
patch link: https://lore.kernel.org/r/20250108114536.627715-3-vdonnefort%40google.com
patch subject: [PATCH v2 02/12] ring-buffer: Introducing ring-buffer remote
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20250110/202501100025.WNnMyW13-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/20250110/202501100025.WNnMyW13-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/202501100025.WNnMyW13-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/trace/ring_buffer.c:2535: warning: Function parameter or struct member 'remote' not described in '__ring_buffer_alloc_remote'
>> kernel/trace/ring_buffer.c:2535: warning: Function parameter or struct member 'key' not described in '__ring_buffer_alloc_remote'
vim +2535 kernel/trace/ring_buffer.c
2528
2529 /**
2530 * __ring_buffer_alloc_remote
2531 *
2532 */
2533 struct trace_buffer *__ring_buffer_alloc_remote(struct ring_buffer_remote *remote,
2534 struct lock_class_key *key)
> 2535 {
2536 return alloc_buffer(0, 0, 0, 0, 0, key, remote);
2537 }
2538
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-09 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 11:45 [PATCH v2 00/12] Tracefs support for pKVM Vincent Donnefort
2025-01-08 11:45 ` [PATCH v2 01/12] ring-buffer: Check for empty ring-buffer with rb_num_of_entries() Vincent Donnefort
2025-01-08 11:45 ` [PATCH v2 02/12] ring-buffer: Introducing ring-buffer remote Vincent Donnefort
2025-01-09 16:45 ` kernel test robot [this message]
2025-01-08 11:45 ` [PATCH v2 03/12] ring-buffer: Expose buffer_data_page material Vincent Donnefort
2025-01-08 11:45 ` [PATCH v2 04/12] KVM: arm64: Support unaligned fixmap in the nVHE hyp Vincent Donnefort
2025-01-08 11:45 ` [PATCH v2 05/12] KVM: arm64: Add clock support " Vincent Donnefort
2025-01-08 11:45 ` [PATCH v2 06/12] KVM: arm64: Add tracing support for the pKVM hyp Vincent Donnefort
2025-01-08 11:45 ` [PATCH v2 07/12] KVM: arm64: Add hyp tracing to tracefs Vincent Donnefort
2025-01-08 11:45 ` [PATCH v2 08/12] KVM: arm64: Add clock for hyp tracefs Vincent Donnefort
2025-01-08 11:45 ` [PATCH v2 09/12] KVM: arm64: Add raw interface " Vincent Donnefort
2025-01-08 11:45 ` [PATCH v2 10/12] KVM: arm64: Add trace " Vincent Donnefort
2025-01-08 11:45 ` [PATCH v2 11/12] KVM: arm64: Add support for hyp events Vincent Donnefort
2025-01-08 11:45 ` [PATCH v2 12/12] KVM: arm64: Add kselftest for tracefs hyp tracefs Vincent Donnefort
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=202501100025.WNnMyW13-lkp@intel.com \
--to=lkp@intel.com \
--cc=joey.gouly@arm.com \
--cc=jstultz@google.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=maz@kernel.org \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oliver.upton@linux.dev \
--cc=qperret@google.com \
--cc=rostedt@goodmis.org \
--cc=suzuki.poulose@arm.com \
--cc=vdonnefort@google.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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