From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] arm/hw_breakpoint.c: Added #include <linux/kdebug.h> instead of<asm/kdebug.h>
Date: Thu, 11 Jun 2015 10:32:07 +0100 [thread overview]
Message-ID: <20150611093207.GA15078@arm.com> (raw)
In-Reply-To: <"000501d0a427$ad431980$07c94c80$@s"@samsung.com>
On Thu, Jun 11, 2015 at 10:18:44AM +0100, Maninder Singh wrote:
> This patch fixes below checkpatch.pl warning:
> WARNING: Use #include <linux/kdebug.h> instead of <asm/kdebug.h>
>
> Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
> Reviewed-by: Vaneet Narang <v.narang@samsung.com>
> ---
> arch/arm/kernel/hw_breakpoint.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/kernel/hw_breakpoint.c b/arch/arm/kernel/hw_breakpoint.c
> index dc7d0a9..86eef81 100644
> --- a/arch/arm/kernel/hw_breakpoint.c
> +++ b/arch/arm/kernel/hw_breakpoint.c
> @@ -35,7 +35,7 @@
> #include <asm/cputype.h>
> #include <asm/current.h>
> #include <asm/hw_breakpoint.h>
> -#include <asm/kdebug.h>
> +#include <linux/kdebug.h>
> #include <asm/traps.h>
> /* Breakpoint currently in use for each BRP. */
afaict, we don't even need the header so we can just drop the #include
altogether. Same for arm64.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Maninder Singh <maninder1.s@samsung.com>
Cc: "linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"v.narang@samsung.com" <v.narang@samsung.com>
Subject: Re: [PATCH 1/1] arm/hw_breakpoint.c: Added #include <linux/kdebug.h> instead of<asm/kdebug.h>
Date: Thu, 11 Jun 2015 10:32:07 +0100 [thread overview]
Message-ID: <20150611093207.GA15078@arm.com> (raw)
In-Reply-To: <"000501d0a427$ad431980$07c94c80$@s"@samsung.com>
On Thu, Jun 11, 2015 at 10:18:44AM +0100, Maninder Singh wrote:
> This patch fixes below checkpatch.pl warning:
> WARNING: Use #include <linux/kdebug.h> instead of <asm/kdebug.h>
>
> Signed-off-by: Maninder Singh <maninder1.s@samsung.com>
> Reviewed-by: Vaneet Narang <v.narang@samsung.com>
> ---
> arch/arm/kernel/hw_breakpoint.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/kernel/hw_breakpoint.c b/arch/arm/kernel/hw_breakpoint.c
> index dc7d0a9..86eef81 100644
> --- a/arch/arm/kernel/hw_breakpoint.c
> +++ b/arch/arm/kernel/hw_breakpoint.c
> @@ -35,7 +35,7 @@
> #include <asm/cputype.h>
> #include <asm/current.h>
> #include <asm/hw_breakpoint.h>
> -#include <asm/kdebug.h>
> +#include <linux/kdebug.h>
> #include <asm/traps.h>
> /* Breakpoint currently in use for each BRP. */
afaict, we don't even need the header so we can just drop the #include
altogether. Same for arm64.
Will
next parent reply other threads:[~2015-06-11 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <"000501d0a427$ad431980$07c94c80$@s"@samsung.com>
2015-06-11 9:32 ` Will Deacon [this message]
2015-06-11 9:32 ` [PATCH 1/1] arm/hw_breakpoint.c: Added #include <linux/kdebug.h> instead of<asm/kdebug.h> Will Deacon
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=20150611093207.GA15078@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.