Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: davinci: remove test for undefined Kconfig macro
Date: Fri, 29 Mar 2013 13:33:25 +0100	[thread overview]
Message-ID: <1364560405.1345.67.camel@x61.thuisdomein> (raw)
In-Reply-To: <1364557655.1345.58.camel@x61.thuisdomein>

[Dropped Kevin Hilman, because Kevin's address bounces.]

On Fri, 2013-03-29 at 12:47 +0100, Paul Bolle wrote:
> The DaVinci debugging macro contains a check for
> CONFIG_DEBUG_DAVINCI_DA8XX_UART0. But there's corresponding Kconfig

                                  [...] there's no corresponding [...]

> symbol, so this test will always evaluate to false. That Kconfig symbol
> is not needed because, as __arch_decomp_setup() shows, there are no
> DaVinci DA8XX boards that use UART0 for debugging. We can remove two
> lines of unneeded code.


Paul Bolle

  reply	other threads:[~2013-03-29 12:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 11:47 [PATCH] ARM: davinci: remove test for undefined Kconfig macro Paul Bolle
2013-03-29 12:33 ` Paul Bolle [this message]
2013-04-02 10:08   ` Sekhar Nori

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=1364560405.1345.67.camel@x61.thuisdomein \
    --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