From: Greg KH <gregkh@linuxfoundation.org>
To: Diederik de Haas <didi.debian@cknow.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
LABBE Corentin <clabbe@baylibre.com>
Subject: Re: crypto-rockchip patches queued for 6.1
Date: Wed, 28 Dec 2022 11:41:40 +0100 [thread overview]
Message-ID: <Y6wdZHlnUIzzreTA@kroah.com> (raw)
In-Reply-To: <2236134.UumAgOJHRH@prancing-pony>
On Wed, Dec 28, 2022 at 11:37:16AM +0100, Diederik de Haas wrote:
> 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?
Please provide us a list of the specific git commits and in the order in
which you wish to see them applied and we will be glad to review them.
Looking at random links (that are wrapped and not able to be easily
used) is not going to work well.
thanks,
greg k-h
next prev parent reply other threads:[~2022-12-28 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 10:37 crypto-rockchip patches queued for 6.1 Diederik de Haas
2022-12-28 10:41 ` Greg KH [this message]
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=Y6wdZHlnUIzzreTA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=clabbe@baylibre.com \
--cc=didi.debian@cknow.org \
--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