public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: <thomas.lendacky@amd.com>, <herbert@gondor.apana.org.au>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Mario Limonciello" <mario.limonciello@amd.com>
Subject: [PATCH 0/3] Fixes for dynamic boost control unit tests
Date: Mon, 28 Aug 2023 14:01:57 -0500	[thread overview]
Message-ID: <20230828190200.1598-1-mario.limonciello@amd.com> (raw)

Further testing of the code being submitted to 6.6-rc1 against
additional hardware found some problems with the unit tests and
sample application.

These patches are produced and tested with the two patches already
posted [1].

Link: https://lore.kernel.org/linux-crypto/20230824221932.2807-1-mario.limonciello@amd.com/#t [1]

Mario Limonciello (3):
  crypto: ccp: Fix DBC sample application error handling
  crypto: ccp: Fix sample application signature passing
  crypto: ccp: Fix some unfused tests

 tools/crypto/ccp/dbc.c       | 17 +++++++++--------
 tools/crypto/ccp/dbc.py      |  8 ++++----
 tools/crypto/ccp/test_dbc.py | 22 +++++++++++-----------
 3 files changed, 24 insertions(+), 23 deletions(-)


base-commit: 85b9bf9a514d991fcecb118d0a8a35e754ff9265
prerequisite-patch-id: 4bcf7f3ea21472e4e28c2457cc9827f6023ec6ca
prerequisite-patch-id: 903be53a20306f0188e52015dbfe5196738bb2eb
-- 
2.34.1


             reply	other threads:[~2023-08-28 19:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28 19:01 Mario Limonciello [this message]
2023-08-28 19:01 ` [PATCH 1/3] crypto: ccp: Fix DBC sample application error handling Mario Limonciello
2023-08-28 19:01 ` [PATCH 2/3] crypto: ccp: Fix sample application signature passing Mario Limonciello
2023-08-28 19:02 ` [PATCH 3/3] crypto: ccp: Fix some unfused tests Mario Limonciello

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=20230828190200.1598-1-mario.limonciello@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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