linux-kernel - Re: [PATCH 5.15 110/317] arm64: dts: renesas: r8a779a0: Update to R-Car Gen4 compatible values

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]

Date: Tue, 2 Apr 2024 19:11:55 -0400
From: Sasha Levin <sashal@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
	Wolfram Sang <wsa+renesas@...g-engineering.com>
Subject: Re: [PATCH 5.15 110/317] arm64: dts: renesas: r8a779a0: Update to
 R-Car Gen4 compatible values

On Tue, Apr 02, 2024 at 10:57:41AM +0200, Geert Uytterhoeven wrote:
>Hi Sasha,
>
>Looks like I missed some things in my previous review...
>
>On Mon, Mar 25, 2024 at 12:36 AM Sasha Levin <sashal@...nel.org> wrote:
>> From: Geert Uytterhoeven <geert+renesas@...der.be>
>>
>> [ Upstream commit a1721bbbdb5c6687d157f8b8714bba837f6028ac ]
>
>This is not the corresponding upstream commit for this commit
>(a022251c2f950cd2 in v5.15.153).
>It should be a1ca409cc050166a9e8ed183c1d4192f511cf6a2.
>How could that happen? Interestingly, the backport in v6.1.83
>(efab55e16c55c637) does have the correct upstream commit.

I suspect that this is me fat-fingering it in an attempt to pull it back
to 5.15 when we had a conversation about it on the mailing list.

[...]

>The Renesas MSIOF driver in v5.15.153 does not handle
>"renesas,rcar-gen4-msiof" yet.  Please backport commit ea9d001550abaf2f
>("spi: sh-msiof: add generic Gen4 binding") in v6.1 to fix that.

I'll grab it, thanks!

-- 
Thanks,
Sasha