From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: virtio-comment@lists.linux.dev, cohuck@redhat.com
Subject: Re: [PATCH] content: Add link for the feature bits chapter
Date: Tue, 11 Jun 2024 19:11:53 -0400 [thread overview]
Message-ID: <20240611190949-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240611175721.2550759-1-parav@nvidia.com>
On Tue, Jun 11, 2024 at 08:57:21PM +0300, Parav Pandit wrote:
> Device common feature bits overview in the basic facilities and
> their actual description are apart by 24 chapters.
>
> Help reader to directly reach out to feature bits definitions from
> the basic chapter.
>
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> ---
> content.tex | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/content.tex b/content.tex
> index 8849522..c3531e2 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -97,12 +97,10 @@ \section{Feature Bits}\label{sec:Basic Facilities of a Virtio Device / Feature B
> Feature bits are allocated as follows:
>
> \begin{description}
> -\item[0 to 23, and 50 to 127] Feature bits for the specific device type
> -
> -\item[24 to 41] Feature bits reserved for extensions to the queue and
> - feature negotiation mechanisms
> -
> -\item[42 to 49, and 128 and above] Feature bits reserved for future extensions.
> +\item\textbf{0 to 23, and 50 to 127} Feature bits for the specific device type
> +\item\textbf{\hyperref[sec:Reserved Feature Bits]{24 to 41}} Feature bits reserved for extensions
> +to the queue and feature negotiation mechanisms
> +\item\textbf{42 to 49, and 128 and above} Feature bits reserved for future extensions.
> \end{description}
Not everyone is browsing online, printing and reading should also work.
So no need to be cute, just add (see \ref[sec:Reserved Feature Bits]) or some such at the end
of the sentence.
> \begin{note}
> --
> 2.34.1
next prev parent reply other threads:[~2024-06-11 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 17:57 [PATCH] content: Add link for the feature bits chapter Parav Pandit
2024-06-11 23:11 ` Michael S. Tsirkin [this message]
2024-06-12 3:51 ` Parav Pandit
2024-06-12 5:40 ` Michael S. Tsirkin
2024-06-12 7:33 ` Parav Pandit
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=20240611190949-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.linux.dev \
/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.