From: Diederik de Haas <didi.debian@cknow.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: LABBE Corentin <clabbe@baylibre.com>
Subject: crypto-rockchip patches queued for 6.1
Date: Wed, 28 Dec 2022 11:37:16 +0100 [thread overview]
Message-ID: <2236134.UumAgOJHRH@prancing-pony> (raw)
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2022-12-28 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 10:37 Diederik de Haas [this message]
2022-12-28 10:41 ` crypto-rockchip patches queued for 6.1 Greg KH
2022-12-28 11:11 ` Diederik de Haas
2022-12-28 13:06 ` Greg KH
2022-12-28 14:50 ` Diederik de Haas
2023-02-03 9:33 ` Greg KH
2023-02-03 11:09 ` Diederik de Haas
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=2236134.UumAgOJHRH@prancing-pony \
--to=didi.debian@cknow.org \
--cc=clabbe@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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