From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: SoC changes for v3.17
Date: Sat, 28 Jun 2014 16:23:02 +0200 [thread overview]
Message-ID: <20140628162302.48b6b835@free-electrons.com> (raw)
In-Reply-To: <20140627124655.GF23978@titan.lakedaemon.net>
Dear Jason Cooper,
On Fri, 27 Jun 2014 08:46:55 -0400, Jason Cooper wrote:
> ----------------------------------------------------------------
> mvebu SoC changes for v3.17
>
> - kirkwood
> - add setup file for netxbig LEDs (non-trivial DT binding doesn't exist yet)
>
> - mvebu
> - staticize where needed
> - add CPU hotplug for Armada XP
> - add public datasheet for Armada XP
It's actually Armada 370 that got a datasheet published.
> - don't apply thermal quirk by default
> - make Aramada 375 external abort logic a quirk
> - update L2/PCIe deadlock workaround after L2CC cleanup
This patch is needed in 3.16, not in 3.17. They really are bug fixes,
fixing a complete system deadlock under PCI load.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-28 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 12:46 [GIT PULL] ARM: mvebu: SoC changes for v3.17 Jason Cooper
2014-06-28 14:23 ` Thomas Petazzoni [this message]
2014-06-28 15:07 ` Jason Cooper
2014-06-28 15:20 ` Thomas Petazzoni
2014-06-29 9:35 ` Russell King - ARM Linux
2014-06-29 9:56 ` Thomas Petazzoni
2014-06-30 10:22 ` Thomas Petazzoni
2014-06-30 10:29 ` Russell King - ARM Linux
2014-06-30 12:06 ` Jason Cooper
2014-06-30 12:11 ` Thomas Petazzoni
2014-06-30 12:14 ` Jason Cooper
2014-06-30 17:44 ` Jason Cooper
2014-06-30 18:50 ` Thomas Petazzoni
2014-07-01 12:11 ` [GIT PULL V2] " Jason Cooper
2014-07-08 5:28 ` 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=20140628162302.48b6b835@free-electrons.com \
--to=thomas.petazzoni@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