From: Yangtao Li <tiny.windzz@gmail.com>
To: ebiederm@xmission.com, akpm@linux-foundation.org,
christian@brauner.io, tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, Yangtao Li <tiny.windzz@gmail.com>
Subject: [PATCH] signal: remove some duplicated includes
Date: Mon, 26 Nov 2018 10:09:00 -0500 [thread overview]
Message-ID: <20181126150900.32235-1-tiny.windzz@gmail.com> (raw)
tty.h and fs.h are included twice.It's unnecessary.
hence just remove them.
Signed-off-by: Yangtao Li <tiny.windzz@gmail.com>
---
kernel/signal.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index 9a32bc2088c9..b319f06e23f7 100644
--- a/kernel/signal.c
+++ b/kernel/signal.c
@@ -19,8 +19,6 @@
#include <linux/sched/task.h>
#include <linux/sched/task_stack.h>
#include <linux/sched/cputime.h>
-#include <linux/fs.h>
-#include <linux/tty.h>
#include <linux/binfmts.h>
#include <linux/coredump.h>
#include <linux/security.h>
--
2.17.0
reply other threads:[~2018-11-26 15:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181126150900.32235-1-tiny.windzz@gmail.com \
--to=tiny.windzz@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=christian@brauner.io \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).