From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: remove redundant preempt.h
Date: Mon, 22 Feb 2016 09:52:05 +0000 [thread overview]
Message-ID: <20160222095205.GA31168@arm.com> (raw)
In-Reply-To: <56C7AE26.1060407@linaro.org>
On Fri, Feb 19, 2016 at 04:07:02PM -0800, Shi, Yang wrote:
> Any comment on this one?
I don't really see the point in it, to be honest. Relying on implicit
#includes is usually a bad idea, there are other files in the kernel
including both of these headers and there's not actually a problem to
fix as far as I can tell.
Will
> On 2/12/2016 9:56 AM, Yang Shi wrote:
> >preempt.h has been included by sched.h, so it is not necessary to include
> >both, just keep sched.h.
> >
> >Signed-off-by: Yang Shi <yang.shi@linaro.org>
> >---
> >Happened to find this when checking preempt.h include for another patch review.
> >Build test is passed with and without CONFIG_PREEMPT enabled.
> >
> > arch/arm64/kernel/cpuinfo.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> >diff --git a/arch/arm64/kernel/cpuinfo.c b/arch/arm64/kernel/cpuinfo.c
> >index 212ae63..e2b37ff 100644
> >--- a/arch/arm64/kernel/cpuinfo.c
> >+++ b/arch/arm64/kernel/cpuinfo.c
> >@@ -25,7 +25,6 @@
> > #include <linux/init.h>
> > #include <linux/kernel.h>
> > #include <linux/personality.h>
> >-#include <linux/preempt.h>
> > #include <linux/printk.h>
> > #include <linux/seq_file.h>
> > #include <linux/sched.h>
> >
>
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: "Shi, Yang" <yang.shi@linaro.org>
Cc: catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] arm64: remove redundant preempt.h
Date: Mon, 22 Feb 2016 09:52:05 +0000 [thread overview]
Message-ID: <20160222095205.GA31168@arm.com> (raw)
In-Reply-To: <56C7AE26.1060407@linaro.org>
On Fri, Feb 19, 2016 at 04:07:02PM -0800, Shi, Yang wrote:
> Any comment on this one?
I don't really see the point in it, to be honest. Relying on implicit
#includes is usually a bad idea, there are other files in the kernel
including both of these headers and there's not actually a problem to
fix as far as I can tell.
Will
> On 2/12/2016 9:56 AM, Yang Shi wrote:
> >preempt.h has been included by sched.h, so it is not necessary to include
> >both, just keep sched.h.
> >
> >Signed-off-by: Yang Shi <yang.shi@linaro.org>
> >---
> >Happened to find this when checking preempt.h include for another patch review.
> >Build test is passed with and without CONFIG_PREEMPT enabled.
> >
> > arch/arm64/kernel/cpuinfo.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> >diff --git a/arch/arm64/kernel/cpuinfo.c b/arch/arm64/kernel/cpuinfo.c
> >index 212ae63..e2b37ff 100644
> >--- a/arch/arm64/kernel/cpuinfo.c
> >+++ b/arch/arm64/kernel/cpuinfo.c
> >@@ -25,7 +25,6 @@
> > #include <linux/init.h>
> > #include <linux/kernel.h>
> > #include <linux/personality.h>
> >-#include <linux/preempt.h>
> > #include <linux/printk.h>
> > #include <linux/seq_file.h>
> > #include <linux/sched.h>
> >
>
next prev parent reply other threads:[~2016-02-22 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 17:56 [PATCH] arm64: remove redundant preempt.h Yang Shi
2016-02-12 17:56 ` Yang Shi
2016-02-20 0:07 ` Shi, Yang
2016-02-20 0:07 ` Shi, Yang
2016-02-22 9:52 ` Will Deacon [this message]
2016-02-22 9:52 ` Will Deacon
2016-02-22 17:03 ` Mark Rutland
2016-02-22 17:03 ` Mark Rutland
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=20160222095205.GA31168@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.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 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.