All of lore.kernel.org
 help / color / mirror / Atom feed
From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: at91: debug: update prompt for DEBUG_AT91_UART
Date: Thu, 15 Oct 2015 16:04:45 +0200	[thread overview]
Message-ID: <20151015140445.GG3421@piout.net> (raw)
In-Reply-To: <1444807482-22797-1-git-send-email-ludovic.desroches@atmel.com>

On 14/10/2015 at 09:24:42 +0200, Ludovic Desroches wrote :
> Add (read help!) to DEBUG_AT91_UART prompt. It is not obvious there are
> such useful information to set DEBUG_UART_PHYS.
> 
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> ---
>  arch/arm/Kconfig.debug | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
> index 259c0ca..589e724 100644
> --- a/arch/arm/Kconfig.debug
> +++ b/arch/arm/Kconfig.debug
> @@ -124,7 +124,7 @@ choice
>  		    0x80024000      | 0xf0024000     | UART9
>  
>  	config DEBUG_AT91_UART
> -		bool "Kernel low-level debugging on Atmel SoCs"
> +		bool "Kernel low-level debugging on Atmel SoCs (read help!)"
>  		depends on ARCH_AT91
>  		help
>  		  Say Y here if you want the debug print routines to direct

Isn't the "read help" message from config DEBUG_LL enough? :)

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Ludovic Desroches <ludovic.desroches@atmel.com>
Cc: plagnioj@jcrosoft.com, nicolas.ferre@atmel.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: at91: debug: update prompt for DEBUG_AT91_UART
Date: Thu, 15 Oct 2015 16:04:45 +0200	[thread overview]
Message-ID: <20151015140445.GG3421@piout.net> (raw)
In-Reply-To: <1444807482-22797-1-git-send-email-ludovic.desroches@atmel.com>

On 14/10/2015 at 09:24:42 +0200, Ludovic Desroches wrote :
> Add (read help!) to DEBUG_AT91_UART prompt. It is not obvious there are
> such useful information to set DEBUG_UART_PHYS.
> 
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> ---
>  arch/arm/Kconfig.debug | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
> index 259c0ca..589e724 100644
> --- a/arch/arm/Kconfig.debug
> +++ b/arch/arm/Kconfig.debug
> @@ -124,7 +124,7 @@ choice
>  		    0x80024000      | 0xf0024000     | UART9
>  
>  	config DEBUG_AT91_UART
> -		bool "Kernel low-level debugging on Atmel SoCs"
> +		bool "Kernel low-level debugging on Atmel SoCs (read help!)"
>  		depends on ARCH_AT91
>  		help
>  		  Say Y here if you want the debug print routines to direct

Isn't the "read help" message from config DEBUG_LL enough? :)

-- 
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-10-15 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14  7:24 [PATCH] ARM: at91: debug: update prompt for DEBUG_AT91_UART Ludovic Desroches
2015-10-14  7:24 ` Ludovic Desroches
2015-10-15 14:04 ` Alexandre Belloni [this message]
2015-10-15 14:04   ` Alexandre Belloni
2015-10-15 15:35   ` Ludovic Desroches
2015-10-15 15:35     ` Ludovic Desroches

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=20151015140445.GG3421@piout.net \
    --to=alexandre.belloni@free-electrons.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.