From: Alexandre Torgue <alexandre.torgue@st.com>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>,
<linux@armlinux.org.uk>, <arnd@arndb.de>,
Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH v2 0/2] ARM errata 814220
Date: Wed, 27 Feb 2019 17:20:56 +0100 [thread overview]
Message-ID: <e25b2626-231b-28d7-93b0-004a21a3685e@st.com> (raw)
In-Reply-To: <20190214083145.15148-1-benjamin.gaignard@linaro.org>
On 2/14/19 9:31 AM, Benjamin Gaignard wrote:
> Implement ARM errata 814220 for Cortex A7.
>
> This patch has been wroten by Jason Liu years ago but never send upstream.
> I have tried to contact the author on multiple email addresses but I haven't
> found any valid one...
> I have keep Jason's sign-off and just rebase the patch on to v5-rc6.
>
> version 2:
> - limite help lines to 80 columns.
> - Add Arnd Bergmann acks.
>
> Benjamin Gaignard (2):
> ARM: errata 814220-B-Cache maintenance by set/way operations can
> execute out of order.
> ARM: stm32: select ARM errata 814220
>
> arch/arm/Kconfig | 12 ++++++++++++
> arch/arm/mach-stm32/Kconfig | 1 +
> arch/arm/mm/cache-v7.S | 3 +++
> 3 files changed, 16 insertions(+)
>
Russel,
If you agree, can I take this series in my STM32 soc tree ?
If yes it will be part of my PR for v5.2.
regards
Alex
next prev parent reply other threads:[~2019-02-27 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 8:31 [PATCH v2 0/2] ARM errata 814220 Benjamin Gaignard
2019-02-14 8:31 ` [PATCH v2 1/2] ARM: errata 814220-B-Cache maintenance by set/way operations can execute out of order Benjamin Gaignard
2019-02-14 8:31 ` [PATCH v2 2/2] ARM: stm32: select ARM errata 814220 Benjamin Gaignard
2019-02-27 16:20 ` Alexandre Torgue [this message]
2019-04-23 17:46 ` [PATCH v2 0/2] " Fabio Estevam
2019-04-24 7:25 ` Benjamin Gaignard
2019-06-11 11:42 ` Benjamin Gaignard
2019-06-11 12:11 ` Russell King - ARM Linux admin
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=e25b2626-231b-28d7-93b0-004a21a3685e@st.com \
--to=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=benjamin.gaignard@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
/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).