From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
kvm@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-s390@vger.kernel.org
Subject: [PATCH next 0/3] miscellaneous documentation fixes for linux-next
Date: Tue, 12 Jul 2022 16:29:51 +0700 [thread overview]
Message-ID: <20220712092954.142027-1-bagasdotme@gmail.com> (raw)
Here are documentation fixes for recent warnings reported in linux-next.
This series is based on next-20220611 and Mauro's cross-ref and doc fixes
series [1]:
[1]: https://lore.kernel.org/linux-doc/cover.1657360984.git.mchehab@kernel.org/
Cc: linux-kernel@vger.kernel.org
Cc: linux-next@vger.kernel.org
Cc: kvm@vger.kernel.org
Cc: linux-crypto@vger.kernel.org
Cc: linux-s390@vger.kernel.org
Bagas Sanjaya (3):
Documentation: qat: Use code block for qat sysfs example
Documentation: qat: rewrite description
Documentation: kvm: extend KVM_S390_ZPCI_OP subheading underline
Documentation/ABI/testing/sysfs-driver-qat | 37 ++++++++--------------
Documentation/virt/kvm/api.rst | 2 +-
2 files changed, 14 insertions(+), 25 deletions(-)
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2022-07-12 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 9:29 Bagas Sanjaya [this message]
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
2022-07-12 21:54 ` Giovanni Cabiddu
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=20220712092954.142027-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@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