public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Paul Bolle <pebolle@tiscali.nl>,
	Jason Cooper <jason@lakedaemon.net>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, arm@kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: Kconfig ARM_ERRATA_753970?
Date: Sun, 06 Apr 2014 19:02:01 +0200	[thread overview]
Message-ID: <53418889.2050002@free-electrons.com> (raw)
In-Reply-To: <1396777049.30640.9.camel@x220>

Hi Paul,

On 06/04/2014 11:37, Paul Bolle wrote:
> On Sat, 2014-04-05 at 20:04 +0100, Arnd Bergmann wrote:
>> Gregory CLEMENT (1):
>>       ARM: mvebu: add initial support for the Armada 375 SOCs
>>
>> [...]
>>
>> Thomas Petazzoni (7):
>>       [...]
>>       ARM: mvebu: add initial support for the Armada 380/385 SOCs
> 
> These two commits added select statements for ARM_ERRATA_753970. But I
> couldn't find that Kconfig symbol. (I checked master of Linus' tree and
> current linux-next.) So it seems it was intended to select
> PL310_ERRATA_753970 here. Is that correct?

Yes it is correct. ARM_ERRATA_753970 was renamed to PL310_ERRATA_753970
in kernel 3.2. I had just carry on the symbol name without noticed that
it have changed.

Do you want to send a fix, or do you prefer I take care of it?


Thanks,

Gregory


> 
> 
> Paul Bolle
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2014-04-06 17:02 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 [this message]
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
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=53418889.2050002@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --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