From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] ARM: mvebu: defconfig for v4.7 (#1)
Date: Thu, 14 Apr 2016 19:12:14 +0200 [thread overview]
Message-ID: <87mvowyv0x.fsf@free-electrons.com> (raw)
Hi,
Here is the first pull request for defconfig for mvebu for v4.7 but in
in his second version after having fixed the patch title.
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 23d2af622de748bf57d31a4125d06d183c29e908:
ARM: mvebu_v5_defconfig: Switching to the new Marvell's cryptographic engine driver (2016-04-14 18:57:19 +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: mvebu_v7_defconfig: Enabling the new Marvell's cryptographic engine driver
ARM: multi_v7_defconfig: Enabling the new Marvell's cryptographic engine driver
ARM: mvebu_v5_defconfig: Switching to the new Marvell's cryptographic engine driver
Thomas Petazzoni (1):
MAINTAINERS: attach arch/arm/configs/mvebu_*_defconfig to relevant maintainers
MAINTAINERS | 2 +-
arch/arm/configs/multi_v7_defconfig | 1 +
arch/arm/configs/mvebu_v5_defconfig | 2 +-
arch/arm/configs/mvebu_v7_defconfig | 1 +
4 files changed, 4 insertions(+), 2 deletions(-)
next reply other threads:[~2016-04-14 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 17:12 Gregory CLEMENT [this message]
2016-04-25 19:10 ` [GIT PULL v2] ARM: mvebu: defconfig for v4.7 (#1) Arnd Bergmann
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=87mvowyv0x.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox