From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Russell King <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, letux-kernel@openphoenux.org,
kernel@pyra-handheld.com, linux-omap@vger.kernel.org
Subject: Re: [PATCH] Kernel debugging: omap: print warning if CONFIG_DEBUG_LL is enabled
Date: Wed, 8 Nov 2017 14:27:55 -0800 [thread overview]
Message-ID: <20171108222755.GW28152@atomide.com> (raw)
In-Reply-To: <b80b85cd6f26d02d698463b3dd5e9783081aa780.1510176592.git.hns@goldelico.com>
* H. Nikolaus Schaller <hns@goldelico.com> [171108 21:32]:
> commit d2b310b0234c ("ARM: debug: Use generic 8250 debug_ll for omap2 and omap3/4/5 common uarts")
> commit fc23beb8a577 ("ARM: debug: Use generic 8250 debug_ll for omap3/4/5")
>
> switched to generic 8250 debug_ll code which seems to be incompatible
> with at least OMAP5 boards (OMAP5EVM, Pyra) if CONFIG_DEBUG_LL is
> still enabled in some legacy defconfig. Since this is very hard to
> relate to these patches and difficult to identify, let's have the
> compiler emit a warning.
Hmm the issue is the existing values in .config as Kconfig.debug
does default XXX if DEBUG_XXX, right?
I think we have this issue in general if you enable DEBUG_LL for
a SoC, then enable it for another SoC using the same .config?
Regards,
Tony
next parent reply other threads:[~2017-11-08 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b80b85cd6f26d02d698463b3dd5e9783081aa780.1510176592.git.hns@goldelico.com>
2017-11-08 22:27 ` Tony Lindgren [this message]
2017-11-08 22:36 ` [PATCH] Kernel debugging: omap: print warning if CONFIG_DEBUG_LL is enabled Russell King - ARM Linux
2017-11-08 22:38 ` Russell King - ARM Linux
2017-11-09 5:44 ` H. Nikolaus Schaller
2017-11-09 16:58 ` Russell King - ARM Linux
2017-11-09 17:16 ` H. Nikolaus Schaller
2017-11-09 17:35 ` Russell King - ARM Linux
2017-11-09 18:12 ` H. Nikolaus Schaller
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=20171108222755.GW28152@atomide.com \
--to=tony@atomide.com \
--cc=hns@goldelico.com \
--cc=kernel@pyra-handheld.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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