From: liuziloong@gmail.com
To: tytso@mit.edu, adilger.kernel@dilger.ca, mhalcrow@google.com
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
"zilong.liu" <liuziloong@gmail.com>
Subject: [PATCH] ext4 crypto: remove duplicate header file
Date: Thu, 16 Jul 2015 15:58:41 +0800 [thread overview]
Message-ID: <1437033521-3138-1-git-send-email-liuziloong@gmail.com> (raw)
From: "zilong.liu" <liuziloong@gmail.com>
Remove key.h which is included twice in crypto_fname.c
Signed-off-by: zilong.liu <liuziloong@gmail.com>
---
fs/ext4/crypto_fname.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/ext4/crypto_fname.c b/fs/ext4/crypto_fname.c
index 7dc4eb5..4c11768 100644
--- a/fs/ext4/crypto_fname.c
+++ b/fs/ext4/crypto_fname.c
@@ -19,7 +19,6 @@
#include <linux/gfp.h>
#include <linux/kernel.h>
#include <linux/key.h>
-#include <linux/key.h>
#include <linux/list.h>
#include <linux/mempool.h>
#include <linux/random.h>
--
1.7.9.5
next reply other threads:[~2015-07-16 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 7:58 liuziloong [this message]
2015-07-28 19:13 ` [PATCH] ext4 crypto: remove duplicate header file Theodore Ts'o
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=1437033521-3138-1-git-send-email-liuziloong@gmail.com \
--to=liuziloong@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@google.com \
--cc=tytso@mit.edu \
/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).