From: kernel test robot <yujie.liu@intel.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: <kbuild-all@lists.01.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [jolsa-perf:bpf/tramp_27 19/33] include/linux/bpf.h: linux/refcount.h is included more than once.
Date: Tue, 12 Jul 2022 14:23:30 +0800 [thread overview]
Message-ID: <93b35388-6b7e-553a-5e09-e72332e1d168@intel.com> (raw)
In-Reply-To: <202207111228.MrXFMOmS-lkp@intel.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git bpf/tramp_27
head: 08201713df8992b94d140b43fd4f20f1ad4aedb3
commit: 4e0c494bd2718df080d359785317d2b9234a79be [19/33] bpf: Add refcount_t to struct bpf_tramp_id
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <yujie.liu@intel.com>
includecheck warnings: (new ones prefixed by >>)
>> include/linux/bpf.h: linux/refcount.h is included more than once.
fc9702273e2ed (Andrii Nakryiko 2019-11-17 09:28:04 -0800 16) #include <linux/mm_types.h>
ab3f0063c48c2 (Jakub Kicinski 2017-11-03 13:56:17 -0700 17) #include <linux/wait.h>
fec56f5890d93 (Alexei Starovoitov 2019-11-14 10:57:04 -0800 @18) #include <linux/refcount.h>
fec56f5890d93 (Alexei Starovoitov 2019-11-14 10:57:04 -0800 19) #include <linux/mutex.h>
85d33df357b63 (Martin KaFai Lau 2020-01-08 16:35:05 -0800 20) #include <linux/module.h>
bfea9a8574f34 (Jiri Olsa 2020-03-12 20:55:59 +0100 21) #include <linux/kallsyms.h>
2c78ee898d8f1 (Alexei Starovoitov 2020-05-13 16:03:54 -0700 22) #include <linux/capability.h>
48edc1f78aabe (Roman Gushchin 2020-12-01 13:58:32 -0800 23) #include <linux/sched/mm.h>
48edc1f78aabe (Roman Gushchin 2020-12-01 13:58:32 -0800 24) #include <linux/slab.h>
e21aa341785c6 (Alexei Starovoitov 2021-03-16 14:00:07 -0700 25) #include <linux/percpu-refcount.h>
d687f621c518d (Delyan Kratunov 2022-06-14 23:10:42 +0000 26) #include <linux/stddef.h>
af2ac3e13e457 (Alexei Starovoitov 2021-05-13 17:36:05 -0700 27) #include <linux/bpfptr.h>
14a324f6a67ef (Kumar Kartikeya Dwivedi 2022-04-25 03:18:55 +0530 28) #include <linux/btf.h>
8c7dcb84e3b74 (Delyan Kratunov 2022-06-14 23:10:46 +0000 29) #include <linux/rcupdate_trace.h>
4e0c494bd2718 (Jiri Olsa 2021-10-12 22:22:08 +0200 @30) #include <linux/refcount.h>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
parent reply other threads:[~2022-07-12 6:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <202207111228.MrXFMOmS-lkp@intel.com>]
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=93b35388-6b7e-553a-5e09-e72332e1d168@intel.com \
--to=yujie.liu@intel.com \
--cc=jolsa@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®