From: Qi Tao <taoqi10@huawei.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<liulongfang@huawei.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>
Subject: [PATCH v2 0/4] some updates and cleanups for hisilicon/sec2.
Date: Fri, 26 Jan 2024 17:21:20 +0800 [thread overview]
Message-ID: <20240126092124.14055-1-taoqi10@huawei.com> (raw)
This seires patch mainly add some RAS registers to enhance the
DFX positioning function and fix some cleanup issues.
[PATCH v1 3/4] -> [PATCH v2 3/4]
sec_sqe3->c_len_ivin |= cpu_to_le32(c_req->c_len);
- sec_sqe3->tag = cpu_to_le64((unsigned long)(uintptr_t)req);
+ sec_sqe3->tag = cpu_to_le64((unsigned long)req);
Other patches are not modified.
Qi Tao (3):
crypto: hisilicon/sec2 - updates the sec DFX function register
crypto: hisilicon/sec2 - modify nested macro call
crypto: hisilicon/sec2 - fix some cleanup issues
Wenkai Lin (1):
crypto: hisilicon/sec - remove unused parameter
drivers/crypto/hisilicon/sec2/sec_crypto.c | 33 ++++++++--------------
drivers/crypto/hisilicon/sec2/sec_main.c | 5 ++++
2 files changed, 17 insertions(+), 21 deletions(-)
--
2.33.0
next reply other threads:[~2024-01-26 9:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 9:21 Qi Tao [this message]
2024-01-26 9:21 ` [PATCH v2 1/4] crypto: hisilicon/sec2 - updates the sec DFX function register Qi Tao
2024-01-26 9:21 ` [PATCH v2 2/4] crypto: hisilicon/sec2 - modify nested macro call Qi Tao
2024-01-26 9:21 ` [PATCH v2 3/4] crypto: hisilicon/sec2 - fix some cleanup issues Qi Tao
2024-01-26 9:21 ` [PATCH v2 4/4] crypto: hisilicon/sec - remove unused parameter Qi Tao
-- strict thread matches above, loose matches on Subject: below --
2024-01-26 9:38 [PATCH v2 0/4] some updates and cleanups for hisilicon/sec2 Qi Tao
2024-02-01 1:58 ` taoqi
2024-02-02 10:11 ` Herbert Xu
2023-12-29 6:44 Qi Tao
2024-01-04 7:58 ` liulongfang
2024-01-19 6:25 ` taoqi
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=20240126092124.14055-1-taoqi10@huawei.com \
--to=taoqi10@huawei.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liulongfang@huawei.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
all inboxes | Powered by JetHome®