From: kernel test robot <lkp@intel.com>
To: <jasperwang@tencent.com>, <kaixuxia@tencent.com>,
<frankjpliu@tencent.com>, <kasong@tencent.com>,
<sagazchen@tencent.com>, <kernelxing@tencent.com>,
<aurelianliu@tencent.com>, <jason.zeng@intel.com>,
<wu.zheng@intel.com>, <yingbao.jia@intel.com>,
<pei.p.jia@intel.com>
Cc: <oe-kbuild-all@lists.linux.dev>
Subject: kernel/cgroup/sli.c: linux/cgroup.h is included more than once.
Date: Fri, 26 Jan 2024 09:43:49 +0800 [thread overview]
Message-ID: <ZbMOVWSLMBng31zl@rli9-mobl> (raw)
tree: https://gitee.com/OpenCloudOS/OpenCloudOS-Kernel.git master
head: 5aef72f74942091b6d408fce235629dc0620e74e
commit: 2690abc40b3ff5bce2553981394ee072eb1f5f66 sli: add sli event monitoring for cgroup
date: 1 year, 9 months ago
:::::: branch date: 34 hours ago
:::::: commit date: 1 year, 9 months ago
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
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/202401260540.7P5Emiq3-lkp@intel.com/
includecheck warnings: (new ones prefixed by >>)
>> kernel/cgroup/sli.c: linux/cgroup.h is included more than once.
vim +3 kernel/cgroup/sli.c
> 3 #include <linux/cgroup.h>
4 #include <linux/module.h>
5 #include <linux/psi.h>
6 #include <linux/memcontrol.h>
7 #include <linux/sched.h>
8 #include <linux/sched/task_stack.h>
9 #include <linux/sched/sysctl.h>
10 #include <linux/stacktrace.h>
11 #include <asm/irq_regs.h>
12 #include "../sched/sched.h"
> 13 #include <linux/cgroup.h>
14 #include <linux/sli.h>
15 #include <linux/rculist.h>
16
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-01-26 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 1:43 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-25 21:47 kernel/cgroup/sli.c: linux/cgroup.h is included more than once 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=ZbMOVWSLMBng31zl@rli9-mobl \
--to=lkp@intel.com \
--cc=aurelianliu@tencent.com \
--cc=frankjpliu@tencent.com \
--cc=jason.zeng@intel.com \
--cc=jasperwang@tencent.com \
--cc=kaixuxia@tencent.com \
--cc=kasong@tencent.com \
--cc=kernelxing@tencent.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pei.p.jia@intel.com \
--cc=sagazchen@tencent.com \
--cc=wu.zheng@intel.com \
--cc=yingbao.jia@intel.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 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.