From: <ye.xingchen@zte.com.cn>
To: brauner@kernel.org
Cc: dchinner@redhat.com, willy@infradead.org,
viro@zeniv.linux.org.uk, reiserfs-devel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] reiserfs: remove duplicate include header in xattr.c
Date: Tue, 7 Mar 2023 15:17:05 +0800 (CST) [thread overview]
Message-ID: <202303071517050653678@zte.com.cn> (raw)
From: Ye Xingchen <ye.xingchen@zte.com.cn>
linux/xattr.h is included more than once.
Signed-off-by: Ye Xingchen <ye.xingchen@zte.com.cn>
---
fs/reiserfs/xattr.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/reiserfs/xattr.c b/fs/reiserfs/xattr.c
index 651027967159..ed1984775a4f 100644
--- a/fs/reiserfs/xattr.c
+++ b/fs/reiserfs/xattr.c
@@ -43,7 +43,6 @@
#include <linux/fs.h>
#include <linux/file.h>
#include <linux/pagemap.h>
-#include <linux/xattr.h>
#include "xattr.h"
#include "acl.h"
#include <linux/uaccess.h>
--
2.25.1
next reply other threads:[~2023-03-07 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 7:17 ye.xingchen [this message]
2023-03-10 10:58 ` [PATCH] reiserfs: remove duplicate include header in xattr.c Christian Brauner
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=202303071517050653678@zte.com.cn \
--to=ye.xingchen@zte.com.cn \
--cc=brauner@kernel.org \
--cc=dchinner@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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 read-only IMAP folder(s) and NNTP newsgroup(s).