From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: soc for v4.4 (#2)
Date: Fri, 16 Oct 2015 19:45:27 +0200 [thread overview]
Message-ID: <87vba6g11k.fsf@free-electrons.com> (raw)
Hi,
Here is the second pull request for soc for mvebu for v4.4.
Gregory
The following changes since commit d492cccac28493f26bb70038385a9ef4df19bdee:
ARM: mvebu: add support to clear shared L2 bit on Armada XP (2015-09-29 15:31:51 +0200)
are available in the git repository at:
git://git.infradead.org/linux-mvebu.git tags/mvebu-soc-4.4-2
for you to fetch changes up to 400b1b26b44f1c5de45bc01873f42c9e776e102e:
ARM: orion5x: use mac_pton() helper (2015-10-15 09:37:18 +0200)
----------------------------------------------------------------
mvebu soc for 4.4 (part 2)
- Use mac_pton() helper in the oropn5x board instead of duplicating it
- Add the broken-idle option allowing to boot boards with a mistake in
the hardware design
----------------------------------------------------------------
Andy Shevchenko (1):
ARM: orion5x: use mac_pton() helper
Vincent Donnefort (1):
ARM: mvebu: add broken-idle option
.../devicetree/bindings/arm/coherency-fabric.txt | 5 ++
arch/arm/mach-mvebu/pmsu.c | 29 ++++++++++--
arch/arm/mach-orion5x/Kconfig | 3 ++
arch/arm/mach-orion5x/dns323-setup.c | 53 ++--------------------
arch/arm/mach-orion5x/tsx09-common.c | 49 ++------------------
5 files changed, 41 insertions(+), 98 deletions(-)
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2015-10-16 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 17:45 Gregory CLEMENT [this message]
2015-10-22 17:41 ` [GIT PULL] ARM: mvebu: soc for v4.4 (#2) 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=87vba6g11k.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;
as well as URLs for NNTP newsgroup(s).