linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: debug: config DEBUG_UART_8250_WORD
Date: Wed, 04 Jun 2014 22:32:46 +0200	[thread overview]
Message-ID: <1401913966.23148.11.camel@x220> (raw)

Russell,

The Kconfig entry for config DEBUG_UART_8250_WORD in
arch/arm/Kconfig.debug contains this dependency:
    depends on DEBUG_UART_8250_SHIFT >= 2

But, as far as I can see, the Kconfig syntax doesn't allow tests like
">=", ">", "<=", etc. And as a result this dependency is (silently!)
parsed as
    depends on DEBUG_UART_8250_SHIFT = 2

Something like this
    depends on DEBUG_UART_8250_SHIFT != "0" && DEBUG_UART_8250_SHIFT != "1"

does what was apparently intended. Should I submit a (basically untested
and) trivial patch to do that? Or would you prefer to find a more
elegant solution yourself?


Paul Bolle

                 reply	other threads:[~2014-06-04 20:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1401913966.23148.11.camel@x220 \
    --to=pebolle@tiscali.nl \
    --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;
as well as URLs for NNTP newsgroup(s).