From: "Michael S. Tsirkin" <mst@redhat.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, kernel@collabora.com
Subject: Re: [PATCH 0/3] docs: driver-api: virtio: documentation improv suggestion
Date: Tue, 20 Dec 2022 06:11:53 -0500 [thread overview]
Message-ID: <20221220061138-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221220095828.27588-1-bagasdotme@gmail.com>
On Tue, Dec 20, 2022 at 04:58:26PM +0700, Bagas Sanjaya wrote:
> Michael S. Tsirkin has asked me [1] to post my improv suggestions for
> now-applied virtio documentation [2], so here is the suggestion patch series.
> The original suggestion must be splitted since it contains three distinct
> changes.
>
> This series is based on kernel-doc fixup posted to fix recent linux-next
> warnings [3].
>
> [1]: https://lore.kernel.org/linux-doc/20221219011647-mutt-send-email-mst@kernel.org/
> [2]: https://lore.kernel.org/linux-doc/Y0QYTq7KW9C731s0@debian.me/
> [3]: https://lore.kernel.org/lkml/20221220073709.2687151-1-ricardo.canuelo@collabora.com/
Thanks, will queue for rc2.
> Bagas Sanjaya (3):
> docs: driver-api: virtio: parenthesize external reference targets
> docs: driver-api: virtio: slightly reword virtqueues allocation
> paragraph
> docs: driver-api: virtio: commentize spec version checking
>
> Documentation/driver-api/virtio/virtio.rst | 19 ++++++++++---------
> 1 file changed, 10 insertions(+), 9 deletions(-)
>
> --
> An old man doll... just what I always wanted! - Clara
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
parent reply other threads:[~2022-12-20 11:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20221220095828.27588-1-bagasdotme@gmail.com>]
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=20221220061138-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=bagasdotme@gmail.com \
--cc=cohuck@redhat.com \
--cc=corbet@lwn.net \
--cc=kernel@collabora.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).