From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: defconfig64 for v4.12 (#2)
Date: Wed, 19 Apr 2017 07:07:20 -0700 [thread overview]
Message-ID: <20170419140720.GP29219@localhost> (raw)
In-Reply-To: <871ssww9zb.fsf@free-electrons.com>
On Thu, Apr 13, 2017 at 06:25:28PM +0200, Gregory CLEMENT wrote:
> Hi,
>
> Here is the second pull request for defconfig64 for mvebu for v4.12.
> There is a trivial merge conflict already solved by Stephen Rothwell
> there:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2017-April/500998.html
>
> Gregory
>
> The following changes since commit 66e56302842e9971426bd7e504c4db4f88cbb037:
>
> arm64: defconfig: enable MVPP2 (2017-03-23 17:50:13 +0100)
>
> are available in the git repository at:
>
> git://git.infradead.org/linux-mvebu.git tags/mvebu-defconfig64-4.12-2
>
> for you to fetch changes up to 10ebb57ffcbf062ff224585fefa274e703fc363d:
>
> arm64: defconfig: enable the Safexcel crypto engine as a module (2017-04-12 15:35:16 +0200)
>
> ----------------------------------------------------------------
> mvebu defconfig64 for 4.12 (part 2)
>
> Select two new drivers for ARM64 mvebu SoCs:
> - Xenon SDHCI controller on Armada 37xx and Armada 7K/8K
> - Safexcel crypto engine on Armada 7K/8K
>
> ----------------------------------------------------------------
> Antoine Tenart (1):
> arm64: defconfig: enable the Safexcel crypto engine as a module
>
> Gregory CLEMENT (1):
> arm64: configs: enable SDHCI driver for Xenon
Merged, thanks!
Please keep an eye on patch prefixes for consistency in the future.
-Olof
next prev parent reply other threads:[~2017-04-19 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 16:25 [GIT PULL] ARM: mvebu: defconfig64 for v4.12 (#2) Gregory CLEMENT
2017-04-19 14:07 ` Olof Johansson [this message]
2017-04-19 15:13 ` Gregory CLEMENT
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=20170419140720.GP29219@localhost \
--to=olof@lixom.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).