From: cgel.zte@gmail.com
To: djwong@kernel.org
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
ran jianping <ran.jianping@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: [PATCH xfs] xfs: remove duplicate include in xfs_super.c
Date: Wed, 27 Oct 2021 08:16:52 +0000 [thread overview]
Message-ID: <20211027081652.1946-1-ran.jianping@zte.com.cn> (raw)
From: ran jianping <ran.jianping@zte.com.cn>
'xfs_btree.h ' included in 'fs/xfs/xfs_super.c'
is duplicated.It is also included on the 40 line.
Reported-by: Zeal Robot <zealci@zte.com.cn>
Signed-off-by: ran jianping <ran.jianping@zte.com.cn>
---
fs/xfs/xfs_super.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
index f4c508428aad..e21459f9923a 100644
--- a/fs/xfs/xfs_super.c
+++ b/fs/xfs/xfs_super.c
@@ -37,7 +37,6 @@
#include "xfs_reflink.h"
#include "xfs_pwork.h"
#include "xfs_ag.h"
-#include "xfs_btree.h"
#include "xfs_defer.h"
#include <linux/magic.h>
--
2.25.1
next reply other threads:[~2021-10-27 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 8:16 cgel.zte [this message]
2021-10-27 20:53 ` [PATCH xfs] xfs: remove duplicate include in xfs_super.c Darrick J. Wong
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=20211027081652.1946-1-ran.jianping@zte.com.cn \
--to=cgel.zte@gmail.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ran.jianping@zte.com.cn \
--cc=zealci@zte.com.cn \
/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