From: kernel test robot <lkp@intel.com>
To: Taeyang Lee <0wn@theori.io>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Peter Zijlstra <peterz@infradead.org>
Subject: [peterz-queue:perf/urgent 1/4] kernel/events/core.c:4732:34: error: expected ';' after top level declarator
Date: Thu, 02 Jul 2026 20:02:30 +0800 [thread overview]
Message-ID: <202607021930.nEzkT5dn-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/urgent
head: 91a15888098678641edd3ef4f5d66fa7e77dcc28
commit: f60c8830996ca8e468f96cc3ae79aab1e6fbfb12 [1/4] perf/core: Detach event groups during remove_on_exec
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20260702/202607021930.nEzkT5dn-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260702/202607021930.nEzkT5dn-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/202607021930.nEzkT5dn-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/events/core.c:4732:34: error: expected ';' after top level declarator
4732 | unsigned long detach_flags)
| ^
| ;
1 error generated.
vim +4732 kernel/events/core.c
4727
4728 static void perf_remove_from_owner(struct perf_event *event);
4729 static void perf_event_exit_event(struct perf_event *event,
4730 struct perf_event_context *ctx,
4731 struct task_struct *task,
> 4732 unsigned long detach_flags)
4733
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-02 12: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=202607021930.nEzkT5dn-lkp@intel.com \
--to=lkp@intel.com \
--cc=0wn@theori.io \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
/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