From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: debug: move StrongARM debug include to arch/arm/include/debug
Date: Mon, 20 Oct 2014 21:43:25 +0200 [thread overview]
Message-ID: <2298192.mGraIjK2LJ@wuerfel> (raw)
In-Reply-To: <1413444696-25790-1-git-send-email-dbaryshkov@gmail.com>
On Thursday 16 October 2014 11:31:36 Dmitry Eremin-Solenikov wrote:
> StrongARM debug-macro.S is quite standalone thing, depending only on
> register mappings. Move it to proper place and add Kconfig entry.
>
> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Looks good to me in principle. Russell, are you ok with us picking this
up through arm-soc?
> arch/arm/Kconfig.debug | 9 +++++++++
> .../include/mach/debug-macro.S => include/debug/sa1100.S} | 10 ++++++++--
> 2 files changed, 17 insertions(+), 2 deletions(-)
> rename arch/arm/{mach-sa1100/include/mach/debug-macro.S => include/debug/sa1100.S} (83%)
>
> diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
> index b11ad54..8adf043 100644
> --- a/arch/arm/Kconfig.debug
> +++ b/arch/arm/Kconfig.debug
> @@ -547,6 +547,14 @@ choice
> Say Y here if you want kernel low-level debugging support
> on PXA UART1.
>
> + config DEBUG_SA1100
> + depends on ARCH_SA1100
> + bool "Use SA1100 UARTs for low-level debug"
> + help
> + Say Y here if you want kernel low-level debugging support
> + on SA-11x0 UART ports. The kernel will check for the first
> + enabled UART in a sequence 3-1-2.
> +
> config DEBUG_REALVIEW_STD_PORT
> bool "RealView Default UART"
> depends on ARCH_REALVIEW
Note that the symbols are ordered alphabetically. Please fix this.
Arnd
next prev parent reply other threads:[~2014-10-20 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 7:31 [PATCH] ARM: debug: move StrongARM debug include to arch/arm/include/debug Dmitry Eremin-Solenikov
2014-10-20 19:43 ` Arnd Bergmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-10 22:44 Dmitry Eremin-Solenikov
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=2298192.mGraIjK2LJ@wuerfel \
--to=arnd@arndb.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox