From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: fixes for v4.7 (#2)
Date: Mon, 04 Jul 2016 22:48:39 +0200 [thread overview]
Message-ID: <8737npw2mw.fsf@free-electrons.com> (raw)
Hi,
Here is the second pull request for fixes for mvebu for v4.7.
Gregory
The following changes since commit 929e604efa3dc0522214e0dc18984be23993e9f0:
ARM: dts: armada-38x: fix MBUS_ID for crypto SRAM on Armada 385 Linksys (2016-06-16 17:01:28 +0200)
are available in the git repository at:
git://git.infradead.org/linux-mvebu.git tags/mvebu-fixes-4.7-2
for you to fetch changes up to b44439e42912b9dcc510a0ff891809ea2cadc46b:
ARM: mvebu: compile pm code conditionally (2016-06-30 13:47:52 +0200)
----------------------------------------------------------------
mvebu fixes for 4.7 (part 2)
Fix a regression introduced by a cleanup on kirkwood_pm_init
----------------------------------------------------------------
Arnd Bergmann (1):
ARM: mvebu: compile pm code conditionally
arch/arm/mach-mvebu/Makefile | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
next reply other threads:[~2016-07-04 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 20:48 Gregory CLEMENT [this message]
2016-07-05 13:57 ` [GIT PULL] ARM: mvebu: fixes for v4.7 (#2) 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=8737npw2mw.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