From: YueHaibing <yuehaibing@huawei.com>
To: darrick.wong@oracle.com, hch@lst.de, dchinner@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
YueHaibing <yuehaibing@huawei.com>
Subject: [PATCH -next] xfs: remove duplicated include
Date: Thu, 27 Jun 2019 15:33:23 +0800 [thread overview]
Message-ID: <20190627073323.45516-1-yuehaibing@huawei.com> (raw)
Remove duplicated include.
Signed-off-by: YueHaibing <yuehaibing@huawei.com>
---
fs/xfs/xfs_extfree_item.c | 1 -
fs/xfs/xfs_filestream.c | 1 -
fs/xfs/xfs_pnfs.c | 1 -
3 files changed, 3 deletions(-)
diff --git a/fs/xfs/xfs_extfree_item.c b/fs/xfs/xfs_extfree_item.c
index 99fd40eb..e515506 100644
--- a/fs/xfs/xfs_extfree_item.c
+++ b/fs/xfs/xfs_extfree_item.c
@@ -13,7 +13,6 @@
#include "xfs_mount.h"
#include "xfs_defer.h"
#include "xfs_trans.h"
-#include "xfs_trans.h"
#include "xfs_trans_priv.h"
#include "xfs_buf_item.h"
#include "xfs_extfree_item.h"
diff --git a/fs/xfs/xfs_filestream.c b/fs/xfs/xfs_filestream.c
index b1869ae..a6d228c 100644
--- a/fs/xfs/xfs_filestream.c
+++ b/fs/xfs/xfs_filestream.c
@@ -21,7 +21,6 @@
#include "xfs_trace.h"
#include "xfs_ag_resv.h"
#include "xfs_trans.h"
-#include "xfs_shared.h"
struct xfs_fstrm_item {
struct xfs_mru_cache_elem mru;
diff --git a/fs/xfs/xfs_pnfs.c b/fs/xfs/xfs_pnfs.c
index 2d95355..6018e1c 100644
--- a/fs/xfs/xfs_pnfs.c
+++ b/fs/xfs/xfs_pnfs.c
@@ -17,7 +17,6 @@
#include "xfs_bmap_util.h"
#include "xfs_error.h"
#include "xfs_iomap.h"
-#include "xfs_shared.h"
#include "xfs_bit.h"
#include "xfs_pnfs.h"
--
2.7.4
next reply other threads:[~2019-06-27 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 7:33 YueHaibing [this message]
2019-06-27 15:26 ` [PATCH -next] xfs: remove duplicated include Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2023-08-10 12:03 [PATCH -next] xfs: Remove " GUO Zihua
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=20190627073323.45516-1-yuehaibing@huawei.com \
--to=yuehaibing@huawei.com \
--cc=darrick.wong@oracle.com \
--cc=dchinner@redhat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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