From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Anubhav Shelat <ashelat@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Shivank Garg <shivankg@amd.com>,
Ackerley Tng <ackerleytng@google.com>,
Fuad Tabba <tabba@google.com>,
Christian Brauner <brauner@kernel.org>,
Sean Christopherson <seanjc@google.com>
Subject: Re: [PATCH v3] tracefs: Add read-only eventfs filesystem at /sys/kernel/events
Date: Thu, 20 Aug 2026 19:25:45 +0800 [thread overview]
Message-ID: <202608201958.Dlhk7OGz-lkp@intel.com> (raw)
In-Reply-To: <20260810160708.3460a2fd@gandalf.local.home>
Hi Steven,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v7.2]
[also build test WARNING on next-20260819]
[cannot apply to trace/for-next linus/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Steven-Rostedt/tracefs-Add-read-only-eventfs-filesystem-at-sys-kernel-events/20260810-160708
base: v7.2
patch link: https://lore.kernel.org/r/20260810160708.3460a2fd%40gandalf.local.home
patch subject: [PATCH v3] tracefs: Add read-only eventfs filesystem at /sys/kernel/events
config: x86_64-randconfig-013-20260820 (https://download.01.org/0day-ci/archive/20260820/202608201958.Dlhk7OGz-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/20260820/202608201958.Dlhk7OGz-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/202608201958.Dlhk7OGz-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: fs/tracefs/event_inode.c:501 function parameter 'ro' not described in 'lookup_dir_entry'
>> Warning: fs/tracefs/event_inode.c:621 function parameter 'ro' not described in '__eventfs_root_lookup'
>> Warning: fs/tracefs/event_inode.c:621 expecting prototype for eventfs_root_lookup(). Prototype was for __eventfs_root_lookup() instead
>> Warning: fs/tracefs/event_inode.c:977 function parameter 'ei' not described in 'eventfs_create_events_ro_copy'
>> Warning: fs/tracefs/event_inode.c:977 expecting prototype for eventfs_create_events_dir_ro(). Prototype was for eventfs_create_events_ro_copy() instead
>> Warning: fs/tracefs/event_inode.c:501 function parameter 'ro' not described in 'lookup_dir_entry'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-08-20 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 20:07 [PATCH v3] tracefs: Add read-only eventfs filesystem at /sys/kernel/events Steven Rostedt
2026-08-10 21:39 ` Steven Rostedt
2026-08-11 1:28 ` Masami Hiramatsu
2026-08-11 1:36 ` Steven Rostedt
2026-08-20 5:32 ` kernel test robot
2026-08-20 11:25 ` kernel test robot [this message]
2026-08-20 11:25 ` 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=202608201958.Dlhk7OGz-lkp@intel.com \
--to=lkp@intel.com \
--cc=ackerleytng@google.com \
--cc=ashelat@redhat.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=shivankg@amd.com \
--cc=tabba@google.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