From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: defconfig for v4.7 (#1)
Date: Wed, 13 Apr 2016 14:47:55 -0700 [thread overview]
Message-ID: <20160413214755.GX19945@localhost> (raw)
In-Reply-To: <87pou1jor9.fsf@free-electrons.com>
Hi,
On Thu, Apr 07, 2016 at 10:46:18AM -0700, Gregory CLEMENT wrote:
> Hi,
>
> Here is the first pull request for defconfig for mvebu for v4.7.
>
> Gregory
>
> The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
>
> Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
>
> are available in the git repository at:
>
> git://git.infradead.org/linux-mvebu.git tags/mvebu-defconfig-4.7-1
>
> for you to fetch changes up to e5a80a6e2f2d1b2afd6439d8f58356e93b77cb2d:
>
> ARM: configs: Switching to the new Marvell's cryptographic engine driver for mvebu_v5_defconfig (2016-03-30 11:51:16 +0200)
>
> ----------------------------------------------------------------
> mvebu defconfig for 4.7 (part 1)
>
> - Use the new cryto engine(mv_cesa) in the mvebu and multi-arm
> defcongig files
> - Attach mvebu_*_defconfig to the mvebu maintainers
>
> ----------------------------------------------------------------
> Romain Perier (3):
> ARM: configs: Enabling the new Marvell's cryptographic engine driver for mvebu_v7_defconfig
> ARM: configs: Enabling the new Marvell's cryptographic engine driver for multi_v7_defconfig
> ARM: configs: Switching to the new Marvell's cryptographic engine driver for mvebu_v5_defconfig
Please use the same format as everybody else:
git log --oneline --no-merges arch/arm/configs
Not pulled, please respin.
-Olof
prev parent reply other threads:[~2016-04-13 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 17:46 [GIT PULL] ARM: mvebu: defconfig for v4.7 (#1) Gregory CLEMENT
2016-04-13 21:47 ` Olof Johansson [this message]
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=20160413214755.GX19945@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 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.