lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87ilapa93w.wl-maz@kernel.org>
Date:   Wed, 12 Jul 2023 08:21:07 +0100
From:   Marc Zyngier <maz@...nel.org>
To:     "Chunhui Li (李春辉)" 
        <chunhui.li@...iatek.com>
Cc:     "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "Hanks Chen (陳彥廷)" 
        <Hanks.Chen@...iatek.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "lpieralisi@...nel.org" <lpieralisi@...nel.org>,
        "Cheng-Yuh Wu (吳政諭)" 
        <Cheng-Yuh.Wu@...iatek.com>
Subject: Re: [PATCH] irqchip/gic-v3: Workaround for GIC-700 erratum 2941627

On Wed, 12 Jul 2023 02:40:31 +0100,
"Chunhui Li (李春辉)" <chunhui.li@...iatek.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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ