public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: debug: Remove unsupported operand from Kconfig.debug
Date: Sun, 14 Jun 2015 20:13:46 +0100	[thread overview]
Message-ID: <20150614191346.GI7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1434306201-21840-1-git-send-email-linux@roeck-us.net>

On Sun, Jun 14, 2015 at 11:23:21AM -0700, Guenter Roeck wrote:
> arm builds show the following warning.
> 
> arch/arm/Kconfig.debug:1576:warning: ignoring unsupported character '>'
> 
> This is due to
> 
> config DEBUG_UART_8250_WORD
> 	bool "Use 32-bit accesses for 8250 UART"
> 	depends on DEBUG_LL_UART_8250 || DEBUG_UART_8250
> 	depends on DEBUG_UART_8250_SHIFT >= 2
> 
> This may create the false expectation that DEBUG_UART_8250_WORD
> is enabled if DEBUG_UART_8250_SHIFT is larger than 2, so drop the '>'.

"is" ?  No, "depends" will control the visibility of this option.

You're quite right that it's expected that the option is visible if
DEBUG_UART_8250_SHIFT is greater than or equal to 2, and that's
actually exactly what we want to express here - and it's entirely
possible for someone to type in a shift greater than two, and that
would also be legal.

I guess if >= 2 doesn't work, what we need instead is:

	depends on DEBUG_UART_8250_SHIFT != 0 &&
		   DEBUG_UART_8250_SHIFT != 1

which would have the same effect.  I also guess that adding a
"range 0 31" or similar to the DEBUG_UART_8250_SHIFT option would
also be a good idea.

Patches to that effect welcome.

Thanks.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

      reply	other threads:[~2015-06-14 19:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 18:23 [PATCH] ARM: debug: Remove unsupported operand from Kconfig.debug Guenter Roeck
2015-06-14 19:13 ` Russell King - ARM Linux [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=20150614191346.GI7557@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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