From: Herbert Xu <herbert@gondor.apana.org.au>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: thomas.lendacky@amd.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] Fixes for dynamic boost control for 6.6
Date: Thu, 31 Aug 2023 17:02:39 +0800 [thread overview]
Message-ID: <ZPBXL0OVXMpp/BUb@gondor.apana.org.au> (raw)
In-Reply-To: <20230829150759.156126-1-mario.limonciello@amd.com>
On Tue, Aug 29, 2023 at 10:07:54AM -0500, Mario Limonciello wrote:
>
> This series fixes all problems found. Ideally all patches should
> be submitted for a future 6.6-rc, but, the most important is
> "crypto: ccp: Get a free page to use while fetching initial nonce"
> if the rest must be pushed to 6.7.
As far as I can see it simply means that the new feature of DBC does
not work. If that's all then I don't think it's an urgent issue and
this can wait until 6.7.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2023-08-31 9:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 15:07 [PATCH v3 0/5] Fixes for dynamic boost control for 6.6 Mario Limonciello
2023-08-29 15:07 ` [PATCH v3 1/5] crypto: ccp: Get a free page to use while fetching initial nonce Mario Limonciello
2023-08-29 15:07 ` [PATCH v3 2/5] crypto: ccp: Fix ioctl unit tests Mario Limonciello
2023-08-29 15:07 ` [PATCH v3 3/5] crypto: ccp: Fix DBC sample application error handling Mario Limonciello
2023-08-29 15:07 ` [PATCH v3 4/5] crypto: ccp: Fix sample application signature passing Mario Limonciello
2023-08-29 15:07 ` [PATCH v3 5/5] crypto: ccp: Fix some unfused tests Mario Limonciello
2023-08-31 9:02 ` Herbert Xu [this message]
2023-08-31 11:27 ` [PATCH v3 0/5] Fixes for dynamic boost control for 6.6 Mario Limonciello
2023-08-31 11:56 ` Herbert Xu
2023-08-31 16:02 ` Mario Limonciello
2023-09-15 10:40 ` Herbert Xu
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=ZPBXL0OVXMpp/BUb@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=thomas.lendacky@amd.com \
/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