From: Greg KH <gregkh@linuxfoundation.org>
To: Kai Ye <yekai13@huawei.com>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, wangzhou1@hisilicon.com
Subject: Re: [PATCH v2 0/4] Documentation: update debugfs doc for Hisilicon Accelerator
Date: Thu, 6 Jan 2022 15:40:23 +0100 [thread overview]
Message-ID: <Ydb/V4HPALDPWgk3@kroah.com> (raw)
In-Reply-To: <20220104082919.45742-1-yekai13@huawei.com>
On Tue, Jan 04, 2022 at 04:29:15PM +0800, Kai Ye wrote:
> Update documentation describing DebugFS for function's QoS limiting.
> Add the note that described how to use the function's QoS limiting.
>
> changes v1->v2:
> fixup the documentation format.
>
> Kai Ye (4):
> Documentation: use the tabs on all acc documentation
> Documentation: update debugfs doc for Hisilicon SEC
> Documentation: update debugfs doc for Hisilicon ZIP
> Documentation: update debugfs doc for Hisilicon HPRE
>
> Documentation/ABI/testing/debugfs-hisi-hpre | 178 +++++++++++---------
> Documentation/ABI/testing/debugfs-hisi-sec | 146 ++++++++--------
> Documentation/ABI/testing/debugfs-hisi-zip | 146 ++++++++--------
> 3 files changed, 250 insertions(+), 220 deletions(-)
>
> --
> 2.33.0
>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2022-01-06 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 8:29 [PATCH v2 0/4] Documentation: update debugfs doc for Hisilicon Accelerator Kai Ye
2022-01-04 8:29 ` [PATCH v2 1/4] Documentation: use the tabs on all acc documentation Kai Ye
2022-01-04 8:29 ` [PATCH v2 2/4] Documentation: update debugfs doc for Hisilicon SEC Kai Ye
2022-01-04 8:29 ` [PATCH v2 3/4] Documentation: update debugfs doc for Hisilicon ZIP Kai Ye
2022-01-04 8:29 ` [PATCH v2 4/4] Documentation: update debugfs doc for Hisilicon HPRE Kai Ye
2022-01-06 14:40 ` Greg KH [this message]
2022-01-28 6:21 ` [PATCH v2 0/4] Documentation: update debugfs doc for Hisilicon Accelerator 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=Ydb/V4HPALDPWgk3@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhou1@hisilicon.com \
--cc=yekai13@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 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.