From: YueHaibing <yuehaibing@huawei.com> To: Alexander Viro <viro@zeniv.linux.org.uk> Cc: YueHaibing <yuehaibing@huawei.com>, <linux-fsdevel@vger.kernel.org>, <kernel-janitors@vger.kernel.org> Subject: [PATCH -next] vfs: syscall: Remove duplicated include from namespace.c Date: Fri, 7 Sep 2018 02:05:37 +0000 [thread overview] Message-ID: <1536285937-150932-1-git-send-email-yuehaibing@huawei.com> (raw) Remove duplicated include. Signed-off-by: YueHaibing <yuehaibing@huawei.com> --- fs/namespace.c | 1 - 1 file changed, 1 deletion(-) diff --git a/fs/namespace.c b/fs/namespace.c index 6c95796..e28db6e 100644 --- a/fs/namespace.c +++ b/fs/namespace.c @@ -26,7 +26,6 @@ #include <linux/magic.h> #include <linux/bootmem.h> #include <linux/task_work.h> -#include <linux/file.h> #include <linux/sched/task.h> #include <uapi/linux/mount.h> #include <linux/fs_context.h>
WARNING: multiple messages have this Message-ID (diff)
From: YueHaibing <yuehaibing@huawei.com> To: Alexander Viro <viro@zeniv.linux.org.uk> Cc: YueHaibing <yuehaibing@huawei.com>, linux-fsdevel@vger.kernel.org, kernel-janitors@vger.kernel.org Subject: [PATCH -next] vfs: syscall: Remove duplicated include from namespace.c Date: Fri, 07 Sep 2018 01:55:33 +0000 [thread overview] Message-ID: <1536285937-150932-1-git-send-email-yuehaibing@huawei.com> (raw) Remove duplicated include. Signed-off-by: YueHaibing <yuehaibing@huawei.com> --- fs/namespace.c | 1 - 1 file changed, 1 deletion(-) diff --git a/fs/namespace.c b/fs/namespace.c index 6c95796..e28db6e 100644 --- a/fs/namespace.c +++ b/fs/namespace.c @@ -26,7 +26,6 @@ #include <linux/magic.h> #include <linux/bootmem.h> #include <linux/task_work.h> -#include <linux/file.h> #include <linux/sched/task.h> #include <uapi/linux/mount.h> #include <linux/fs_context.h>
next reply other threads:[~2018-09-07 6:33 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-09-07 1:55 YueHaibing [this message] 2018-09-07 2:05 ` [PATCH -next] vfs: syscall: Remove duplicated include from namespace.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=1536285937-150932-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: linkBe 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.