[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86y2x5xhti.wl-maz@kernel.org>
Date: Mon, 28 Oct 2019 10:52:57 +0000
From: Marc Zyngier <maz@...nel.org>
To: Zenghui Yu <yuzenghui@...wei.com>
Cc: <kvmarm@...ts.cs.columbia.edu>, <linux-kernel@...r.kernel.org>,
Eric Auger <eric.auger@...hat.com>,
James Morse <james.morse@....com>,
Julien Thierry <julien.thierry.kdev@...il.com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
"Andrew Murray" <Andrew.Murray@....com>,
Jayachandran C <jnair@...vell.com>,
"Robert Richter" <rrichter@...vell.com>
Subject: Re: [PATCH v2 04/36] irqchip/gic-v3-its: Make is_v4 use a TYPER copy
On Mon, 28 Oct 2019 09:34:42 +0000,
Zenghui Yu <yuzenghui@...wei.com> wrote:
>
> Hi Marc,
>
> On 2019/10/27 22:42, Marc Zyngier wrote:
> > Instead of caching the GICv4 compatibility in a discrete way, cache the
> > TYPER register instead, which can then be used to implement the same
> > functionnality. This will get used more extensively in subsequent patches.
> >
> > Signed-off-by: Marc Zyngier <maz@...nel.org>
>
> nit: You may need to rebase some patches on top of mainline when
> you finally decide to take them in, i.e., as we currently have
> get_its_list(), which will use the legacy its->is_v4.
Yeah, I was planning on rebasing the whole irqchip-next branch on top
of -rc5 to avoid this kind of problems.
> Reviewed-by: Zenghui Yu <yuzenghui@...wei.com>
Thanks for that.
M.
--
Jazz is not dead, it just smells funny.
Powered by blists - more mailing lists