The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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,
	xuzaibo@huawei.com
Subject: Re: [PATCH 1/3] Documentation: update debugfs doc for Hisilicon SEC
Date: Sun, 26 Dec 2021 11:45:54 +0100	[thread overview]
Message-ID: <YchH4g+mhfRQKXoX@kroah.com> (raw)
In-Reply-To: <20211225062718.41155-2-yekai13@huawei.com>

On Sat, Dec 25, 2021 at 02:27:16PM +0800, Kai Ye wrote:
> Update documentation describing DebugFS for function's QoS limiting.
> 
> Signed-off-by: Kai Ye <yekai13@huawei.com>
> ---
>  Documentation/ABI/testing/debugfs-hisi-sec | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/Documentation/ABI/testing/debugfs-hisi-sec b/Documentation/ABI/testing/debugfs-hisi-sec
> index 85feb4408e0f..9e50ceab94d2 100644
> --- a/Documentation/ABI/testing/debugfs-hisi-sec
> +++ b/Documentation/ABI/testing/debugfs-hisi-sec
> @@ -14,6 +14,16 @@ Description:    One SEC controller has one PF and multiple VFs, each function
>  		qm refers to.
>  		Only available for PF.
>  
> +What:           /sys/kernel/debug/hisi_sec2/<bdf>/alg_qos
> +Date:           Jun 2021
> +Contact:        linux-crypto@vger.kernel.org

No tabs?  Why not?

thanks,

greg k-h

  reply	other threads:[~2021-12-26 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-25  6:27 [PATCH 0/3] Documentation: update debugfs doc for Hisilicon Accelerator Kai Ye
2021-12-25  6:27 ` [PATCH 1/3] Documentation: update debugfs doc for Hisilicon SEC Kai Ye
2021-12-26 10:45   ` Greg KH [this message]
2022-01-04  6:46     ` yekai(A)
2021-12-25  6:27 ` [PATCH 2/3] Documentation: update debugfs doc for Hisilicon ZIP Kai Ye
2021-12-25  6:27 ` [PATCH 3/3] Documentation: update debugfs doc for Hisilicon HPRE Kai Ye

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=YchH4g+mhfRQKXoX@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=xuzaibo@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox