From: YueHaibing <yuehaibing@huawei.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Yue Haibing <yuehaibing@huawei.com>,
<linux-fsdevel@vger.kernel.org>,
<kernel-janitors@vger.kernel.org>
Subject: [PATCH -next] iomap: remove duplicated include from iomap.c
Date: Thu, 6 Sep 2018 01:54:07 +0000 [thread overview]
Message-ID: <1536198847-10922-1-git-send-email-yuehaibing@huawei.com> (raw)
From: Yue Haibing <yuehaibing@huawei.com>
Remove duplicated include.
Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
---
fs/iomap.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/iomap.c b/fs/iomap.c
index 009071e..e837c36 100644
--- a/fs/iomap.c
+++ b/fs/iomap.c
@@ -30,7 +30,6 @@
#include <linux/task_io_accounting_ops.h>
#include <linux/dax.h>
#include <linux/sched/signal.h>
-#include <linux/swap.h>
#include "internal.h"
WARNING: multiple messages have this Message-ID (diff)
From: YueHaibing <yuehaibing@huawei.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Yue Haibing <yuehaibing@huawei.com>,
linux-fsdevel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: [PATCH -next] iomap: remove duplicated include from iomap.c
Date: Thu, 06 Sep 2018 01:54:07 +0000 [thread overview]
Message-ID: <1536198847-10922-1-git-send-email-yuehaibing@huawei.com> (raw)
From: Yue Haibing <yuehaibing@huawei.com>
Remove duplicated include.
Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
---
fs/iomap.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/iomap.c b/fs/iomap.c
index 009071e..e837c36 100644
--- a/fs/iomap.c
+++ b/fs/iomap.c
@@ -30,7 +30,6 @@
#include <linux/task_io_accounting_ops.h>
#include <linux/dax.h>
#include <linux/sched/signal.h>
-#include <linux/swap.h>
#include "internal.h"
next reply other threads:[~2018-09-06 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 1:54 YueHaibing [this message]
2018-09-06 1:54 ` [PATCH -next] iomap: remove duplicated include from iomap.c YueHaibing
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=1536198847-10922-1-git-send-email-yuehaibing@huawei.com \
--to=yuehaibing@huawei.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.