From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org, linux-next@vger.kernel.org
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: [PATCH RESEND v2 0/2] Documentation: qat: documentation fixes
Date: Wed, 13 Jul 2022 15:56:26 +0700 [thread overview]
Message-ID: <20220713085627.175604-1-bagasdotme@gmail.com> (raw)
Here are documentation fixes for qat driver, as recently reported in
linux-next. This is resend of [1], due to missing v2 subject prefix.
Sorry for noise.
Changes since v1 [2]:
- based on next-20220712
- Drop kvms390 (already applied by respective maintainer)
- Focused on qat driver
- Drop "initialize" from [2/2]
- Collect Acked-by from Giovanni Cabiddu
[1]: https://lore.kernel.org/linux-doc/20220713030332.158525-1-bagasdotme@gmail.com/
[2]: https://lore.kernel.org/linux-doc/20220712092954.142027-1-bagasdotme@gmail.com/
Cc: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org
Bagas Sanjaya (2):
Documentation: qat: Use code block for qat sysfs example
Documentation: qat: rewrite description
Documentation/ABI/testing/sysfs-driver-qat | 37 ++++++++--------------
1 file changed, 13 insertions(+), 24 deletions(-)
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2022-07-13 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 8:56 Bagas Sanjaya [this message]
2022-07-13 8:56 ` [PATCH RESEND v2 1/2] Documentation: qat: Use code block for qat sysfs example Bagas Sanjaya
2022-07-13 13:00 ` Vlad Dronov
2022-07-22 8:44 ` Herbert Xu
2022-07-13 8:56 ` [PATCH RESEND v2 2/2] Documentation: qat: rewrite description Bagas Sanjaya
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=20220713085627.175604-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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