From: Jack Xu <jack.xu@intel.com>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, qat-linux@intel.com,
Jack Xu <jack.xu@intel.com>
Subject: [PATCH 0/5] crypto: qat - fix firmware loader
Date: Mon, 17 May 2021 05:13:11 -0400 [thread overview]
Message-ID: <20210517091316.69630-1-jack.xu@intel.com> (raw)
This patchset is to fix some issues in the QAT firmware loader:
* Patches #1 to #3, check the MMP binary size and return error if too large
* Patch #4 fixes a problem detected by clang static
* Patch #5 fixes a compiling warnings when building with clang
Jack Xu (5):
crypto: qat - return error when failing to map FW
crypto: qat - check MMP size before writing to the SRAM
crypto: qat - report an error if MMP file size is too large
crypto: qat - check return code of qat_hal_rd_rel_reg()
crypto: qat - remove unused macro in FW loader
.../qat/qat_common/icp_qat_fw_loader_handle.h | 2 +-
drivers/crypto/qat/qat_common/qat_hal.c | 14 +++++++++-----
drivers/crypto/qat/qat_common/qat_uclo.c | 12 +++++-------
3 files changed, 15 insertions(+), 13 deletions(-)
--
2.31.1
next reply other threads:[~2021-05-17 8:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 9:13 Jack Xu [this message]
2021-05-17 9:13 ` [PATCH 1/5] crypto: qat - return error when failing to map FW Jack Xu
2021-05-17 9:13 ` [PATCH 2/5] crypto: qat - check MMP size before writing to the SRAM Jack Xu
2021-05-17 9:13 ` [PATCH 3/5] crypto: qat - report an error if MMP file size is too large Jack Xu
2021-05-17 9:13 ` [PATCH 4/5] crypto: qat - check return code of qat_hal_rd_rel_reg() Jack Xu
2021-05-17 9:13 ` [PATCH 5/5] crypto: qat - remove unused macro in FW loader Jack Xu
2021-05-28 7:24 ` [PATCH 0/5] crypto: qat - fix firmware loader 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=20210517091316.69630-1-jack.xu@intel.com \
--to=jack.xu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=qat-linux@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.