public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-doc@vger.kernel.org, Adam Guerin <adam.guerin@intel.com>,
	Tomasz Kowallik <tomaszx.kowalik@intel.com>,
	Wojciech Ziemba <wojciech.ziemba@intel.com>,
	Fiona Trahe <fiona.trahe@intel.com>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH next 2/3] Documentation: qat: rewrite description
Date: Tue, 12 Jul 2022 12:33:20 +0100	[thread overview]
Message-ID: <Ys1cAIxILX3nboqq@silpixa00400314> (raw)
In-Reply-To: <20220712092954.142027-3-bagasdotme@gmail.com>

On Tue, Jul 12, 2022 at 04:29:53PM +0700, Bagas Sanjaya wrote:
> The sysfs description contains redundancy on returned and allowed values
> list, due to the described sysfs is read-write. Rewrite.
> 
> Cc: Adam Guerin <adam.guerin@intel.com>
> Cc: Tomasz Kowallik <tomaszx.kowalik@intel.com>
> Cc: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
> Cc: Wojciech Ziemba <wojciech.ziemba@intel.com>
> Cc: Fiona Trahe <fiona.trahe@intel.com>
> Cc: linux-crypto@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Acked-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>

-- 
Giovanni

  reply	other threads:[~2022-07-12 11:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12  9:29 [PATCH next 0/3] miscellaneous documentation fixes for linux-next Bagas Sanjaya
2022-07-12  9:29 ` [PATCH next 1/3] Documentation: qat: Use code block for qat sysfs example Bagas Sanjaya
2022-07-12 11:32   ` Giovanni Cabiddu
2022-07-12  9:29 ` [PATCH next 2/3] Documentation: qat: rewrite description Bagas Sanjaya
2022-07-12 11:33   ` Giovanni Cabiddu [this message]
2022-07-12 21:54   ` Giovanni Cabiddu
2022-07-12  9:29 ` [PATCH next 3/3] Documentation: kvm: extend KVM_S390_ZPCI_OP subheading underline Bagas Sanjaya
2022-07-12  9:38   ` Christian Borntraeger

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=Ys1cAIxILX3nboqq@silpixa00400314 \
    --to=giovanni.cabiddu@intel.com \
    --cc=adam.guerin@intel.com \
    --cc=bagasdotme@gmail.com \
    --cc=fiona.trahe@intel.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomaszx.kowalik@intel.com \
    --cc=wojciech.ziemba@intel.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