From: Marc Zyngier <maz@kernel.org>
To: "\"Chunhui Li (李春辉)\"" <chunhui.li@mediatek.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"\"Hanks Chen (陳彥廷)\"" <Hanks.Chen@mediatek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
"\"Cheng-Yuh Wu (吳政諭)\"" <Cheng-Yuh.Wu@mediatek.com>
Subject: Re: [PATCH] irqchip/gic-v3: Workaround for GIC-700 erratum 2941627
Date: Wed, 12 Jul 2023 08:21:07 +0100 [thread overview]
Message-ID: <87ilapa93w.wl-maz@kernel.org> (raw)
In-Reply-To: <17c629f00dee2bbcd09b99a6ed1bd2a411322084.camel@mediatek.com>
On Wed, 12 Jul 2023 02:40:31 +0100,
"Chunhui Li (李春辉)" <chunhui.li@mediatek.com> wrote:
>
> Hi Marc,
>
> We have tested the PATCH v2 with MTK platform base on kernel-6.1 and
> can confirm that it works as expected.
Thanks.
> Is the PATCH v2 final version?
Nothing is final until it is merged upstream. The patch is currently
in -next. If it doesn't cause any visible regression, I'll send it to
Thomas to push it to Linus.
> If yes, maybe we can request google sync the PATCH v2 to android14-6.1
> first.
That's for you to discuss with the Android team, but from my point of
view, things have to happen upstream first, and only then be
backported to older kernels as required, not the other way around.
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2023-07-12 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17c629f00dee2bbcd09b99a6ed1bd2a411322084.camel@mediatek.com>
2023-07-12 7:21 ` Marc Zyngier [this message]
[not found] <ed3c5fe3f7ed42d58d98e77b3513d6eabf2ad6cd.camel@mediatek.com>
2023-07-09 8:20 ` [PATCH] irqchip/gic-v3: Workaround for GIC-700 erratum 2941627 Marc Zyngier
2023-07-10 6:00 ` Chunhui Li (李春辉)
2023-07-11 2:03 ` Chunhui Li (李春辉)
2023-07-04 12:34 Lorenzo Pieralisi
2023-07-04 14:44 ` Marc Zyngier
2023-07-04 15:14 ` Lorenzo Pieralisi
2023-07-04 15:23 ` Marc Zyngier
2023-07-04 15:27 ` Lorenzo Pieralisi
2023-07-04 15:31 ` Marc Zyngier
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=87ilapa93w.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Cheng-Yuh.Wu@mediatek.com \
--cc=Hanks.Chen@mediatek.com \
--cc=chunhui.li@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
/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).