All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
Cc: linux-doc@vger.kernel.org,
	virtualization@lists.linux-foundation.org, mst@redhat.com,
	jasowang@redhat.com, kernel@collabora.com, cohuck@redhat.com
Subject: Re: [PATCH v2 2/2] docs: driver-api: virtio: virtio on Linux
Date: Sat, 6 Aug 2022 14:58:08 +0700	[thread overview]
Message-ID: <Yu4fEEDMVrC7eNY1@debian.me> (raw)
In-Reply-To: <20220804105914.3707389-3-ricardo.canuelo@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 2253 bytes --]

On Thu, Aug 04, 2022 at 12:59:14PM +0200, Ricardo Cañuelo wrote:
> +References
> +==========
> +
> +[1] Virtio Spec v1.2:
> +https://docs.oasis-open.org/virtio/virtio/v1.2/virtio-v1.2.html
> +
> +Check for later versions of the spec as well.
> +
> +[2] Virtqueues and virtio ring: How the data travels
> +https://www.redhat.com/en/blog/virtqueues-and-virtio-ring-how-data-travels
> +
> +.. rubric:: Footnotes
> +
> +.. [#f1] that's why they may be also referred as virtrings.

Sphinx citation syntax can be used for external references, like:

diff --git a/Documentation/driver-api/virtio/virtio.rst b/Documentation/driver-api/virtio/virtio.rst
index 4b73c705c94c61..abd682cfd41eda 100644
--- a/Documentation/driver-api/virtio/virtio.rst
+++ b/Documentation/driver-api/virtio/virtio.rst
@@ -50,8 +50,8 @@ similar to the ones used in a network device:
 All the buffers the descriptors point to are allocated by the guest and
 used by the host either for reading or for writing but not for both.
 
-Refer to Chapter 2.5 ("Virtqueues") of the virtio spec [1] for the
-reference definitions of virtqueues and to [2] for an illustrated
+Refer to Chapter 2.5 ("Virtqueues") of the virtio spec [1]_ for the
+reference definitions of virtqueues and to [2]_ for an illustrated
 overview of how the host device and the guest driver communicate.
 
 The :c:type:`vring_virtqueue` struct models a virtqueue, including the
@@ -138,13 +138,13 @@ calling a transport-specific ``find_vqs`` method.
 References
 ==========
 
-[1] Virtio Spec v1.2:
-https://docs.oasis-open.org/virtio/virtio/v1.2/virtio-v1.2.html
+.. [1] Virtio Spec v1.2:
+   https://docs.oasis-open.org/virtio/virtio/v1.2/virtio-v1.2.html
 
-Check for later versions of the spec as well.
+   Check for later versions of the spec as well.
 
-[2] Virtqueues and virtio ring: How the data travels
-https://www.redhat.com/en/blog/virtqueues-and-virtio-ring-how-data-travels
+.. [2] Virtqueues and virtio ring: How the data travels
+   https://www.redhat.com/en/blog/virtqueues-and-virtio-ring-how-data-travels
 
 .. rubric:: Footnotes
 

Otherwise the documentation LGTM (no new warnings).

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]

  reply	other threads:[~2022-08-06  7:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 10:59 [PATCH v2 0/2] docs: driver-api: virtio: virtio on Linux Ricardo Cañuelo
2022-08-04 10:59 ` Ricardo Cañuelo
2022-08-04 10:59 ` [PATCH v2 1/2] virtio: kerneldocs fixes and enhancements Ricardo Cañuelo
2022-08-04 10:59   ` Ricardo Cañuelo
2022-08-08 12:14   ` Cornelia Huck
2022-08-08 12:14     ` Cornelia Huck
2022-08-08 12:52     ` Ricardo Cañuelo
2022-08-08 12:52       ` Ricardo Cañuelo
2022-08-04 10:59 ` [PATCH v2 2/2] docs: driver-api: virtio: virtio on Linux Ricardo Cañuelo
2022-08-04 10:59   ` Ricardo Cañuelo
2022-08-06  7:58   ` Bagas Sanjaya [this message]
2022-08-08  9:06     ` Ricardo Cañuelo
2022-08-08  9:06       ` Ricardo Cañuelo
2022-08-08 12:31       ` Bagas Sanjaya
2022-08-08 13:47   ` Cornelia Huck
2022-08-08 13:47     ` Cornelia Huck
2022-08-09 13:05     ` Ricardo Cañuelo
2022-08-09 13:05       ` Ricardo Cañuelo
2022-08-09 14:28       ` Cornelia Huck
2022-08-09 14:28         ` Cornelia Huck

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=Yu4fEEDMVrC7eNY1@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=cohuck@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kernel@collabora.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=ricardo.canuelo@collabora.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.