linux-kernel - Re: [PATCH v2 5/5] phy: mvebu-sata: prepare new Dove DT Kconfig variable

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: <531398FC.6020405@gmail.com>
Date:	Sun, 02 Mar 2014 21:47:56 +0100
From:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To:	Kishon Vijay Abraham I <kishon@...com>
CC:	Jason Cooper <jason@...edaemon.net>, Andrew Lunn <andrew@...n.ch>,
	Gregory Clement <gregory.clement@...e-electrons.com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 5/5] phy: mvebu-sata: prepare new Dove DT Kconfig variable

On 03/01/2014 02:38 PM, Kishon Vijay Abraham I wrote:
> On Saturday 01 March 2014 02:03 PM, Sebastian Hesselbarth wrote:
>> DT-enabled Dove will move over from ARCH_DOVE in mach-dove to
>> MACH_DOVE in
>> mach-mvebu. As non-DT ARCH_DOVE will stay to rot for a while, add a new
>> DT-only MACH_DOVE Kconfig.
>>
>> Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
>> ---
>> Kishon,
>>
>> Mark Brown requested to take the corresponding ASoC patch through
>> his tree. Therefore, I have split the former patch into individual
>> subsystem
>> patches. This patch also received an update, to not break bisectability
>> we add DT-enabled MACH_DOVE and maintain ARCH_DOVE, which is non-DT only
>> after conversion. ARCH_DOVE will be removed, when legacy mach-dove will
>> be removed.
>
> Cool.. Should this patch be going through PHY tree?

Yes, please pick it up.

Thanks,
   Sebastian

--
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/