From: gregory.clement@bootlin.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: dt64 for v4.19 (#2)
Date: Tue, 31 Jul 2018 11:32:53 +0200 [thread overview]
Message-ID: <87h8kfda2i.fsf@bootlin.com> (raw)
In-Reply-To: <20180721213352.eborr5dctfk3t7j3@localhost> (Olof Johansson's message of "Sat, 21 Jul 2018 14:33:52 -0700")
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
next prev parent reply other threads:[~2018-07-31 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 8:54 [GIT PULL] ARM: mvebu: dt64 for v4.19 (#2) Gregory CLEMENT
2018-07-21 21:33 ` Olof Johansson
2018-07-31 9:32 ` Gregory CLEMENT [this message]
2018-08-01 2:07 ` Olof Johansson
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=87h8kfda2i.fsf@bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.