From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/2] ARM: PJ4B: fix for 3.10-rc
Date: Fri, 7 Jun 2013 11:12:34 +0100 [thread overview]
Message-ID: <20130607101234.GF3132@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1370599460-9947-1-git-send-email-gregory.clement@free-electrons.com>
On Fri, Jun 07, 2013 at 11:04:18AM +0100, Gregory CLEMENT wrote:
> Hello,
>
> This path set allows to fix one errata for PJ4B CPUs.
>
> Without this the Armada 370 based board can't boot anymore since
> 3.10-rc1. So this one really need to be applied on 3.10-rc.
>
> As they were pending question for the second one, I preferred to keep
> it apart awaiting the answers from the Marvell engineer.
>
> Both of the patches of this series are needed to fix the issue. Indeed
> if the CPU is not recognized as a PJ4B then the fix is not applied.
Reviewed-by: Will Deacon <will.deacon@arm.com>
Does this need a CC stable as well? I know that my TLB patch tickled it, but
that's not to say it couldn't occur with particular configurations of older
kernels.
Will
next prev parent reply other threads:[~2013-06-07 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 10:04 [PATCH v4 0/2] ARM: PJ4B: fix for 3.10-rc Gregory CLEMENT
2013-06-07 10:04 ` [PATCH v4 1/2] ARM: PJ4B: Fix the CPU ID and the mask associated to the PJ4B Gregory CLEMENT
2013-06-07 10:04 ` [PATCH v4 2/2] ARM PJ4B: Add support for errata 4742 Gregory CLEMENT
2013-06-08 2:09 ` Nicolas Pitre
2013-06-17 8:31 ` Russell King - ARM Linux
2013-06-07 10:12 ` Will Deacon [this message]
2013-06-07 11:50 ` [PATCH v4 0/2] ARM: PJ4B: fix for 3.10-rc Gregory CLEMENT
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=20130607101234.GF3132@mudshark.cambridge.arm.com \
--to=will.deacon@arm.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).