All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/3] soc: renesas: ARM errata updates
Date: Fri, 23 Aug 2019 10:35:11 +0200	[thread overview]
Message-ID: <CAMuHMdX6Z9oe3kbkNr00dkfckxBTForrEnOZLWSBE-8EFGtFAw@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdWj7eCa9URtztqth=fYMn2uTHWDS3WAKnRvxDfMjjBH_A@mail.gmail.com>

On Fri, Aug 23, 2019 at 9:54 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Wed, Aug 21, 2019 at 2:46 PM Geert Uytterhoeven
> <geert+renesas@glider.be> wrote:
> > This patch series updates the handling of ARM errata for affected
> > Renesas SoCs.
> >
> > The first patch enables the new ARM_ERRATA_814220 for Cortex-A7, using
> > Kconfig logic.
>
> Queuing the first one in renesas-devel for v5.4.
>
> > The second patch moves enablement of ARM_ERRATA_754322 for Cortex-A9
> > from shmobile_defconfig to Kconfig logic, to make sure it's always
> > enabled when needed.
> > The third patch disables PL310_ERRATA_588369, as it doesn't affect any
> > Renesas SoCs.
> >
> > The last patch is marked RFC, as I don't know the revision of PL310 on
> > EMMA Mobile EV2, and cannot test it on EMEV2.
>
> The other 2 are postponed.

Given it untangles dependencies, I'm also queuing the Kconfig part of patch 2.
The defconfig update will happen automatically during the refresh
after v5.4-rc1.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/3] soc: renesas: ARM errata updates
Date: Fri, 23 Aug 2019 10:35:11 +0200	[thread overview]
Message-ID: <CAMuHMdX6Z9oe3kbkNr00dkfckxBTForrEnOZLWSBE-8EFGtFAw@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdWj7eCa9URtztqth=fYMn2uTHWDS3WAKnRvxDfMjjBH_A@mail.gmail.com>

On Fri, Aug 23, 2019 at 9:54 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Wed, Aug 21, 2019 at 2:46 PM Geert Uytterhoeven
> <geert+renesas@glider.be> wrote:
> > This patch series updates the handling of ARM errata for affected
> > Renesas SoCs.
> >
> > The first patch enables the new ARM_ERRATA_814220 for Cortex-A7, using
> > Kconfig logic.
>
> Queuing the first one in renesas-devel for v5.4.
>
> > The second patch moves enablement of ARM_ERRATA_754322 for Cortex-A9
> > from shmobile_defconfig to Kconfig logic, to make sure it's always
> > enabled when needed.
> > The third patch disables PL310_ERRATA_588369, as it doesn't affect any
> > Renesas SoCs.
> >
> > The last patch is marked RFC, as I don't know the revision of PL310 on
> > EMMA Mobile EV2, and cannot test it on EMEV2.
>
> The other 2 are postponed.

Given it untangles dependencies, I'm also queuing the Kconfig part of patch 2.
The defconfig update will happen automatically during the refresh
after v5.4-rc1.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-08-23  8:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21 12:45 [PATCH 0/3] soc: renesas: ARM errata updates Geert Uytterhoeven
2019-08-21 12:45 ` Geert Uytterhoeven
2019-08-21 12:46 ` [PATCH 1/3] soc: renesas: Enable ARM_ERRATA_814220 for affected Cortex-A7 Geert Uytterhoeven
2019-08-21 12:46   ` Geert Uytterhoeven
2019-08-22  8:58   ` Simon Horman
2019-08-22  8:58     ` Simon Horman
2019-08-21 12:46 ` [PATCH 2/3] soc: renesas: Enable ARM_ERRATA_754322 for affected Cortex-A9 Geert Uytterhoeven
2019-08-21 12:46   ` Geert Uytterhoeven
2019-08-22  8:59   ` Simon Horman
2019-08-22  8:59     ` Simon Horman
2019-08-21 12:46 ` [PATCH 3/3] [RFC] ARM: shmobile: defconfig: Disable PL310_ERRATA_588369 Geert Uytterhoeven
2019-08-21 12:46   ` Geert Uytterhoeven
2019-08-22  8:58   ` Simon Horman
2019-08-22  8:58     ` Simon Horman
2019-08-23  9:49     ` Geert Uytterhoeven
2019-08-23  9:49       ` Geert Uytterhoeven
2019-08-23  7:54 ` [PATCH 0/3] soc: renesas: ARM errata updates Geert Uytterhoeven
2019-08-23  7:54   ` Geert Uytterhoeven
2019-08-23  8:35   ` Geert Uytterhoeven [this message]
2019-08-23  8:35     ` Geert Uytterhoeven

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=CAMuHMdX6Z9oe3kbkNr00dkfckxBTForrEnOZLWSBE-8EFGtFAw@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=geert+renesas@glider.be \
    --cc=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.