From: Zhou Wang <wangzhou1@hisilicon.com>
To: Colin King <colin.king@canonical.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.or
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][crypto-next] crypto: hisilicon: fix spelling mistake "HZIP_COMSUMED_BYTE" -> "HZIP_CONSU
Date: Mon, 12 Aug 2019 13:06:58 +0000 [thread overview]
Message-ID: <5D516472.4000905@hisilicon.com> (raw)
In-Reply-To: <20190812111525.574-1-colin.king@canonical.com>
On 2019/8/12 19:15, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in the hzip_dfx_regs array, fix this.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/crypto/hisilicon/zip/zip_main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/hisilicon/zip/zip_main.c b/drivers/crypto/hisilicon/zip/zip_main.c
> index 6e0ca75585d4..00ecae387fdd 100644
> --- a/drivers/crypto/hisilicon/zip/zip_main.c
> +++ b/drivers/crypto/hisilicon/zip/zip_main.c
> @@ -206,7 +206,7 @@ static struct debugfs_reg32 hzip_dfx_regs[] = {
> {"HZIP_AVG_DELAY ", 0x28ull},
> {"HZIP_MEM_VISIBLE_DATA ", 0x30ull},
> {"HZIP_MEM_VISIBLE_ADDR ", 0x34ull},
> - {"HZIP_COMSUMED_BYTE ", 0x38ull},
> + {"HZIP_CONSUMED_BYTE ", 0x38ull},
Yes, thanks.
Zhou
> {"HZIP_PRODUCED_BYTE ", 0x40ull},
> {"HZIP_COMP_INF ", 0x70ull},
> {"HZIP_PRE_OUT ", 0x78ull},
>
prev parent reply other threads:[~2019-08-12 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 11:15 [PATCH][crypto-next] crypto: hisilicon: fix spelling mistake "HZIP_COMSUMED_BYTE" -> "HZIP_CONSUMED_ Colin King
2019-08-12 13:06 ` Zhou Wang [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=5D516472.4000905@hisilicon.com \
--to=wangzhou1@hisilicon.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-crypto@vger.kernel.or \
--cc=linux-kernel@vger.kernel.org \
/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 NNTP newsgroup(s).