From: kernel test robot <rong.a.chen@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
netdev@vger.kernel.org
Subject: [RFC PATCH tip] sched/headers, net: fix duplicated inclusion
Date: Tue, 15 Jun 2021 09:13:10 +0800 [thread overview]
Message-ID: <20210615011310.GR237458@shao2-debian> (raw)
In-Reply-To: <20210615011224.GQ237458@shao2-debian>
kernel/bpf/inode.c: linux/seq_file.h is included more than once.
Generated by: scripts/checkincludes.pl
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
inode.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/kernel/bpf/inode.c b/kernel/bpf/inode.c
index 5a86998df2e3e..b7df5e30b5163 100644
--- a/kernel/bpf/inode.c
+++ b/kernel/bpf/inode.c
@@ -14,7 +14,6 @@
#include <linux/mount.h>
#include <linux/namei.h>
#include <linux/sysfs.h>
-#include <linux/seq_file.h>
#include <linux/kmod.h>
#include <linux/fs.h>
#include <linux/fs_context.h>
next prev parent reply other threads:[~2021-06-15 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 1:12 [tip:tmp.tmp2 341/364] kernel/bpf/inode.c: linux/seq_file.h is included more than once kernel test robot
2021-06-15 1:13 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-15 1:10 [tip:tmp.tmp2 324/364] net/core/sock.c: linux/poll.h " kernel test robot
2021-06-15 1:11 ` [RFC PATCH tip] sched/headers, net: fix duplicated inclusion 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=20210615011310.GR237458@shao2-debian \
--to=rong.a.chen@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kbuild-all@lists.01.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=x86@kernel.org \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).