linux-kernel - Re: ARM: mvebu: CONFIG_DEBUG_MVEBU_UART

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150112130430.GC19533@lunn.ch>
Date:	Mon, 12 Jan 2015 14:04:30 +0100
From:	Andrew Lunn <andrew@...n.ch>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Maxime Ripard <maxime.ripard@...e-electrons.com>,
	Jason Cooper <jason@...edaemon.net>,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	Gregory CLEMENT <gregory.clement@...e-electrons.com>,
	linux-arm-kernel@...ts.infradead.org,
	Valentin Rothberg <valentinrothberg@...il.com>
Subject: Re: ARM: mvebu: CONFIG_DEBUG_MVEBU_UART_ALTERNATE

On Mon, Jan 12, 2015 at 10:33:56AM +0100, Paul Bolle wrote:
> Maxime,
> 
> Your commit d91125ddf962 ("ARM: mvebu: Rename DEBUG_LL to indicate UART
> index") is included in today's linux-next (ie, next-20150112). So is the
> related commit bd920490047a ("ARM: mvebu: Add UART1 as DEBUG_LL possible
> target"). I noticed because a script I use, spotted a minor issue with
> the first commit.
> 
> See, the first commit renamed DEBUG_MVEBU_UART_ALTERNATE to
> DEBUG_MVEBU_UART0_ALTERNATE (so "0" was added). But there's still a last
> reference to CONFIG_DEBUG_MVEBU_UART_ALTERNATE in a comment in
> arch/arm/boot/dts/armada-xp-axpwifiap.dts. Is a patch to rename that
> last reference queued somewhere? If not, should I submit a trivial patch
> to do that?

Hi Paul

Nothing queued, so please do submit a patch.

Thanks
	Andrew
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/