[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150922190932.4391652a@arm.com>
Date: Tue, 22 Sep 2015 19:09:32 +0100
From: Marc Zyngier <marc.zyngier@....com>
To: Robert Richter <rric@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Tirumalesh Chalamarla <tchalamarla@...ium.com>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
Robert Richter <rrichter@...ium.com>,
Catalin Marinas <Catalin.Marinas@....com>,
Will Deacon <Will.Deacon@....com>
Subject: Re: [PATCH v5 0/6] irqchip, gicv3: Updates and Cavium ThunderX
errata workarounds
On Tue, 22 Sep 2015 17:57:01 +0100
Marc Zyngier <marc.zyngier@....com> wrote:
[Duh. Now with Will and Catalin on CC]
> On Mon, 21 Sep 2015 22:58:33 +0200
> Robert Richter <rric@...nel.org> wrote:
>
> > From: Robert Richter <rrichter@...ium.com>
> >
> > This patch series adds gicv3 updates and workarounds for HW errata in
> > Cavium's ThunderX GICV3.
> >
> > The patches has been rebased onto 4.3-rc1. Note that there are two
> > important fixes. See below for all changes.
> >
> > The first one is an unchanged resubmission of a patch from a gicv3
> > series I sent a while ago.
> >
> > The next patches implement the workarounds for ThunderX's gicv3. Patch
> > #2 implements the cpu workaround for gicv3 on ThunderX. Patch #3 is a
> > prerequisit for patch #5. Patch #4 adds generic code to parse the hw
> > revision provided by an IIDR. This patch is used for the implementa-
> > tion of the actual gicv3-its workaround in #5. Patch #6 updates to the
> > new jump label API.
> >
> > All current review comments addressed so far with v5
>
> Catalin, Will: assuming you don't have any objection to this series,
> how do you want to deal with patch 2?
>
> Thanks,
>
> M.
--
Jazz is not dead. It just smells funny.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists