From: liulongfang <liulongfang@huawei.com>
To: Qi Tao <taoqi10@huawei.com>, <herbert@gondor.apana.org.au>,
<davem@davemloft.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] some updates and cleanups for hisilicon/sec2.
Date: Thu, 4 Jan 2024 15:58:42 +0800 [thread overview]
Message-ID: <ce0455d4-49c7-4838-a774-e7834aac5904@huawei.com> (raw)
In-Reply-To: <20231229064421.16981-1-taoqi10@huawei.com>
On 2023/12/29 14:44, Qi Tao wrote:
> This seires patch mainly add some RAS registers to enhance the
> DFX positioning function and fix some cleanup issues.
>
> 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(-)
>
Reviewed-by: Longfang Liu <liulongfang@huawei.com>
Thanks,
Longfang.
next prev parent reply other threads:[~2024-01-04 7:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 6:44 Qi Tao
2023-12-29 6:44 ` [PATCH 1/4] crypto: hisilicon/sec2 - updates the sec DFX function register Qi Tao
2023-12-29 6:44 ` [PATCH 2/4] crypto: hisilicon/sec2 - modify nested macro call Qi Tao
2023-12-29 6:44 ` [PATCH 3/4] crypto: hisilicon/sec2 - fix some cleanup issues Qi Tao
2024-01-25 9:37 ` Herbert Xu
2024-01-26 8:40 ` taoqi
2024-01-26 8:54 ` Herbert Xu
2023-12-29 6:44 ` [PATCH 4/4] crypto: hisilicon/sec - remove unused parameter Qi Tao
2024-01-04 7:58 ` liulongfang [this message]
2024-01-19 6:25 ` [PATCH v2 0/4] some updates and cleanups for hisilicon/sec2 taoqi
2024-01-26 9:21 Qi Tao
2024-01-26 9:38 Qi Tao
2024-02-01 1:58 ` taoqi
2024-02-02 10:11 ` 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=ce0455d4-49c7-4838-a774-e7834aac5904@huawei.com \
--to=liulongfang@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=taoqi10@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®