From: rkuo <rkuo@codeaurora.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linux-hexagon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Hexagon: remove check for CONFIG_COMET_EARLY_UART_DEBUG
Date: Tue, 20 May 2014 19:26:58 -0500 [thread overview]
Message-ID: <20140521002658.GG12698@codeaurora.org> (raw)
In-Reply-To: <1400327586.13824.10.camel@x220>
On Sat, May 17, 2014 at 01:53:06PM +0200, Paul Bolle wrote:
> There's been a check for CONFIG_COMET_EARLY_UART_DEBUG ever since
> Hexagon was added in v3.2. But the related Kconfig symbol has never been
> added to the tree. Remove this check.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> Not tested.
>
> arch/hexagon/kernel/vm_init_segtable.S | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/arch/hexagon/kernel/vm_init_segtable.S b/arch/hexagon/kernel/vm_init_segtable.S
> index 80967f2192b3..167b48458620 100644
> --- a/arch/hexagon/kernel/vm_init_segtable.S
> +++ b/arch/hexagon/kernel/vm_init_segtable.S
> @@ -85,12 +85,7 @@ swapper_pg_dir:
> .word X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X
> .word X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X,X
> /*0xa8*/.word X,X,X,X
> -#ifdef CONFIG_COMET_EARLY_UART_DEBUG
> -UART_PTE_ENTRY:
> -/*0xa9*/.word BKPG_IO(0xa9000000),BKPG_IO(0xa9000000),BKPG_IO(0xa9000000),BKPG_IO(0xa9000000)
> -#else
> /*0xa9*/.word X,X,X,X
> -#endif
> /*0xaa*/.word X,X,X,X
> /*0xab*/.word X,X,X,X
> /*0xac*/.word X,X,X,X
> --
> 1.9.0
>
Thanks, I'll include this in my next set, or it can go via anyone else's.
Acked-by: Ricahrd Kuo <rkuo@codeaurora.org>
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
prev parent reply other threads:[~2014-05-21 0:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 11:53 [PATCH] Hexagon: remove check for CONFIG_COMET_EARLY_UART_DEBUG Paul Bolle
2014-05-21 0:26 ` rkuo [this message]
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=20140521002658.GG12698@codeaurora.org \
--to=rkuo@codeaurora.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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).