From mboxrd@z Thu Jan  1 00:00:00 1970
From: gregory.clement@bootlin.com (Gregory CLEMENT)
Date: Tue, 31 Jul 2018 11:32:53 +0200
Subject: [GIT PULL] ARM: mvebu: dt64 for v4.19 (#2)
In-Reply-To: <20180721213352.eborr5dctfk3t7j3@localhost> (Olof Johansson's
 message of "Sat, 21 Jul 2018 14:33:52 -0700")
References: <87sh4e8eym.fsf@bootlin.com>
 <20180721213352.eborr5dctfk3t7j3@localhost>
Message-ID: <87h8kfda2i.fsf@bootlin.com>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

Hi Olof,
 
 On sam., juil. 21 2018, Olof Johansson <olof@lixom.net> wrote:

> On Fri, Jul 20, 2018 at 10:54:25AM +0200, Gregory CLEMENT wrote:
>> Hi,
>> 
>> Here is the second pull request for dt64 for mvebu for v4.19.
>> 
>> Gregory
>> 
>> The following changes since commit 4436a3711e3249840e0679e92d3c951bcaf25515:
>> 
>>   arm64: dts: marvell: armada-37xx: reserve memory for ATF (2018-06-29 16:39:03 +0200)
>> 
>> are available in the Git repository at:
>> 
>>   git://git.infradead.org/linux-mvebu.git tags/mvebu-dt64-4.19-2
>> 
>> for you to fetch changes up to c462f6c77e72804b72e008a91c4b6fa8d9b4b265:
>> 
>>   arm64: dts: marvell: armada-37xx: update the crypto engine compatible (2018-07-13 13:42:03 +0200)
>> 
>> ----------------------------------------------------------------
>> mvebu dt64 for 4.19 (part 2)
>> 
>> Use more specific compatible for the Inside Secure SafeXcel on the
>> Armada 37xx and the Armada 7K/8K SoCs.
>
> I'll reply to the patches -- usually compatible should go from specific to
> generic and you're replacing here instead of adding a more specific first. You
> probably want to do the former instead.
>
> Not merged, let's settle discussion on the patch first.

Now that Antoine explained the reason for replacing the compatible, will
you pull the branch?

Gregory

>
>
> -Olof

-- 
Gregory Clement, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com