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
Subject: [RFC PATCH tip] sched/headers, rcu: fix duplicated inclusion
Date: Tue, 15 Jun 2021 09:04:30 +0800 [thread overview]
Message-ID: <20210615010430.GH237458@shao2-debian> (raw)
In-Reply-To: <20210615010331.GG237458@shao2-debian>
fs/ocfs2/dir.c: linux/iversion.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>
---
dir.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/ocfs2/dir.c b/fs/ocfs2/dir.c
index 158ee3abe75f7..b70375994bf3d 100644
--- a/fs/ocfs2/dir.c
+++ b/fs/ocfs2/dir.c
@@ -27,7 +27,6 @@
#include <linux/quotaops.h>
#include <linux/sort.h>
#include <linux/iversion.h>
-#include <linux/iversion.h>
#include <linux/sched/signal.h>
#include <cluster/masklog.h>
prev parent reply other threads:[~2021-06-15 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 1:03 [tip:tmp.tmp2 176/364] fs/ocfs2/dir.c: linux/iversion.h is included more than once kernel test robot
2021-06-15 1:04 ` kernel test robot [this message]
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=20210615010430.GH237458@shao2-debian \
--to=rong.a.chen@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).