linux-kernel - crypto-rockchip patches queued for 6.1

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-next>] [day] [month] [year] [list]

Message-ID: <2236134.UumAgOJHRH@prancing-pony>
Date:   Wed, 28 Dec 2022 11:37:16 +0100
From:   Diederik de Haas <didi.debian@...ow.org>
To:     linux-kernel@...r.kernel.org, stable@...r.kernel.org
Cc:     LABBE Corentin <clabbe@...libre.com>
Subject: crypto-rockchip patches queued for 6.1

Hi,

I couldn't find an existing mail with "[PATCH AUTOSEL 6.1 N/M] XYZ" to reply 
to, so I'm just sending an email like this. Hope that's ok.

In https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/
tree/queue-6.1 there are a number of patches which start with:
crypto-rockchip- like crypto-rockchip-add-fallback-for-ahash.patch

I guess they were (auto) selected as they contain a "Fixes: <commitid>" line. 
Those 7 patches are actually part of a larger patch set, see here:
https://lore.kernel.org/all/20220927075511.3147847-1-clabbe@baylibre.com/

All those patches have been merged into Linus' tree for 6.2 and there's a 
hotfix planned to be submitted for 6.2 here:
https://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/
commit/?h=v6.2-armsoc/dtsfixes&id=53e8e1e6e9c1653095211a8edf17912f2374bb03

Wouldn't it make more sense to queue the whole patch set for 6.1?
Or (at least) the whole crypto rockchip part as mentioned here:
https://lore.kernel.org/all/Y5mGGrBJaDL6mnQJ@gondor.apana.org.au/ 
under the "Corentin Labbe (32):" label?

Cheers,
  Diederik
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)