From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jason Cooper <jason@lakedaemon.net>
Cc: Paul Bolle <pebolle@tiscali.nl>, Andrew Lunn <andrew@lunn.ch>,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: mvebu: rename ARM_ERRATA_753970
Date: Fri, 20 Jun 2014 21:53:40 +0100 [thread overview]
Message-ID: <20140620205340.GX32514@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140620202100.GG21711@titan.lakedaemon.net>
On Fri, Jun 20, 2014 at 04:21:00PM -0400, Jason Cooper wrote:
> It looks like rmk just added a patch to fixing the selection of the
> erratas. Could you please take a look and either rebase or drop this
> patch?
Yes please. If it's needed, just update it to be:
> > diff --git a/arch/arm/mach-mvebu/Kconfig b/arch/arm/mach-mvebu/Kconfig
> > index 3f73eecbcfb0..501d0f42e7b2 100644
> > --- a/arch/arm/mach-mvebu/Kconfig
> > +++ b/arch/arm/mach-mvebu/Kconfig
> > @@ -35,7 +35,7 @@ config MACH_ARMADA_370
> > config MACH_ARMADA_375
> > bool "Marvell Armada 375 boards" if ARCH_MULTI_V7
> > select ARM_ERRATA_720789
> > - select ARM_ERRATA_753970
> > + select PL310_ERRATA_753970 if CACHE_PL310
select PL310_ERRATA_753970 if CACHE_L2X0
for both platforms. Although there's no harm in using CACHE_PL310 at
the moment, my longer term plan is to eventually kill CACHE_PL310 as
it's entirely redundant for ARM versions of the L2 cache (it's only
used by the old L2x0 code which I've been unable to eliminate entirely.)
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-06-20 20:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 19:01 [GIT PULL 0/8] ARM: SoC: pending changes for 3.15 Arnd Bergmann
2014-04-05 19:02 ` [GIT PULL 1/8] ARM: SoC non-critical bug fixes " Arnd Bergmann
2014-04-05 19:03 ` [GIT PULL 2/8] ARM: SoC: cleanups " Arnd Bergmann
2014-04-05 19:04 ` [GIT PULL 3/8] ARM: SoC specific changes Arnd Bergmann
2014-04-06 9:37 ` Kconfig ARM_ERRATA_753970? Paul Bolle
2014-04-06 17:02 ` Gregory CLEMENT
2014-04-06 17:28 ` Paul Bolle
2014-05-26 9:01 ` [PATCH] ARM: mvebu: rename ARM_ERRATA_753970 Paul Bolle
2014-06-20 20:21 ` Jason Cooper
2014-06-20 20:42 ` Paul Bolle
2014-06-20 21:10 ` Jason Cooper
2014-06-23 7:58 ` Paul Bolle
2014-06-20 20:53 ` Russell King - ARM Linux [this message]
2014-06-23 9:01 ` [PATCH v2] " Paul Bolle
2014-06-23 9:07 ` Russell King - ARM Linux
2014-06-23 9:34 ` Paul Bolle
2014-09-12 11:10 ` [PATCH v3] " Paul Bolle
2014-09-12 13:31 ` Russell King - ARM Linux
2014-11-05 9:11 ` Paul Bolle
2014-04-05 19:04 ` [GIT PULL 4/8] ARM: SoC: board changes Arnd Bergmann
2014-04-05 19:05 ` [GIT PULL 5/8] ARM: SoC: device tree changes Arnd Bergmann
2014-04-05 19:06 ` [GIT PULL 6/8] ARM: SoC: driver changes Arnd Bergmann
2014-04-05 19:06 ` [GIT PULL 7/8] ARM: SoC: sh " Arnd Bergmann
2014-04-05 19:07 ` [GIT PULL 8/8] ARM: SoC: late cleanups 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=20140620205340.GX32514@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
/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
all inboxes | Powered by JetHome®