From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [android-common:android16-6.12 5/5] mm/rmap.c: trace/hooks/mm.h is included more than once.
Date: Thu, 5 Jun 2025 10:15:33 +0800 [thread overview]
Message-ID: <202506051010.edVtXapp-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: cros-kernel-buildreports@googlegroups.com
tree: https://android.googlesource.com/kernel/common android16-6.12
head: 7a02c9f4a3ec528bc3b99ff4475e9823225c4f04
commit: 79376c98694f31a642dc7765eb726d1bb1f6378d [5/5] ANDROID: vendor_hooks: Add hook in try_to_unmap_one()
:::::: branch date: 9 hours ago
:::::: commit date: 9 hours ago
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
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/r/202506051010.edVtXapp-lkp@intel.com/
includecheck warnings: (new ones prefixed by >>)
>> mm/rmap.c: trace/hooks/mm.h is included more than once.
vim +86 mm/rmap.c
81
82 #define CREATE_TRACE_POINTS
83 #include <trace/events/tlb.h>
84 #include <trace/events/migrate.h>
85 #undef CREATE_TRACE_POINTS
> 86 #include <trace/hooks/mm.h>
87
88 #undef CREATE_TRACE_POINTS
> 89 #include <trace/hooks/mm.h>
90
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-06-05 2:16 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=202506051010.edVtXapp-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.