linux-kernel - Re: [PATCH v4 03/12] serial: mvebu-uart: initial support for Armada-3700 serial port

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <2634634.yW5ZfZDXSz@wuerfel>
Date:	Tue, 16 Feb 2016 22:35:14 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	linux-arm-kernel@...ts.infradead.org
Cc:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Mark Rutland <mark.rutland@....com>,
	Andrew Lunn <andrew@...n.ch>,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	Nadav Haklai <nadavh@...vell.com>, linux-ide@...r.kernel.org,
	Lior Amsalem <alior@...vell.com>,
	Jonathan Corbet <corbet@....net>, arm@...nel.org,
	linux-serial@...r.kernel.org, Jiri Slaby <jslaby@...e.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
	devicetree@...r.kernel.org, Jason Cooper <jason@...edaemon.net>,
	Omri Itach <omrii@...vell.com>,
	Hans de Goede <hdegoede@...hat.com>,
	Gregory CLEMENT <gregory.clement@...e-electrons.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org>,
	Wilson Ding <dingwei@...vell.com>
Subject: Re: [PATCH v4 03/12] serial: mvebu-uart: initial support for Armada-3700 serial port

On Tuesday 16 February 2016 22:27:06 Thomas Petazzoni wrote:
> Arnd,
> 
> On Tue, 16 Feb 2016 22:20:51 +0100, Arnd Bergmann wrote:
> 
> > > +config SERIAL_MVEBU_CONSOLE
> > > +       bool "Console on Marvell EBU serial port"
> > > +       depends on SERIAL_MVEBU_UART
> > 
> > then this one must become
> > 
> >       depends on SERIAL_MVEBU_UART
> > 
> > so it does not get enabled if the driver is not builtin.
> 
> Hm, what's the different between "depends on SERIAL_MVEBU_UART" and
> "depends on SERIAL_MVEBU_UART" ? Is it the late time that causes my
> eyes to misunderstand what you mean, or some typo on your side ? 
> 


typo: I meant

	depends on SERIAL_MVEBU_UART=y


	Arnd