From: Herbert Xu <herbert@gondor.apana.org.au>
To: Chenghai Huang <huangchenghai2@huawei.com>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, fanghao11@huawei.com,
liulongfang@huawei.com, shenyang39@huawei.com,
songzhiqi1@huawei.com, qianweili@huawei.com,
liushangbin@hisilicon.com, linwenkai6@hisilicon.com,
taoqi10@huawei.com, wangzhou1@hisilicon.com
Subject: Re: [PATCH 0/2] crypto: hisilicon - fix reg offset issue and cleanup dump information
Date: Fri, 3 May 2024 18:54:02 +0800 [thread overview]
Message-ID: <ZjTCSolBz4aNW_VA@gondor.apana.org.au> (raw)
In-Reply-To: <20240423011922.770693-1-huangchenghai2@huawei.com>
On Tue, Apr 23, 2024 at 09:19:20AM +0800, Chenghai Huang wrote:
> Fix for register offset and cleanup dump information of debugfs.
>
> Chenghai Huang (1):
> crypto: hisilicon/debugfs - mask the unnecessary info from the dump
>
> Wenkai Lin (1):
> crypto: hisilicon/sec2 - fix for register offset
>
> drivers/crypto/hisilicon/debugfs.c | 29 +++++++++++++++--------
> drivers/crypto/hisilicon/hpre/hpre_main.c | 2 +-
> drivers/crypto/hisilicon/sec2/sec_main.c | 6 ++---
> 3 files changed, 23 insertions(+), 14 deletions(-)
>
> --
> 2.30.0
All applied. Thanks.
--
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
prev parent reply other threads:[~2024-05-03 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 1:19 [PATCH 0/2] crypto: hisilicon - fix reg offset issue and cleanup dump information Chenghai Huang
2024-04-23 1:19 ` [PATCH 1/2] crypto: hisilicon/debugfs - mask the unnecessary info from the dump Chenghai Huang
2024-04-23 1:19 ` [PATCH 2/2] crypto: hisilicon/sec2 - fix for register offset Chenghai Huang
2024-05-03 10:54 ` Herbert Xu [this message]
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=ZjTCSolBz4aNW_VA@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=fanghao11@huawei.com \
--cc=huangchenghai2@huawei.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linwenkai6@hisilicon.com \
--cc=liulongfang@huawei.com \
--cc=liushangbin@hisilicon.com \
--cc=qianweili@huawei.com \
--cc=shenyang39@huawei.com \
--cc=songzhiqi1@huawei.com \
--cc=taoqi10@huawei.com \
--cc=wangzhou1@hisilicon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).