public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.linux.dev>, <mst@redhat.com>,
	<cohuck@redhat.com>, <mvaralar@redhat.com>
Cc: <shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [PATCH] virtio-net: editorial: Annotate structure field
Date: Fri, 18 Oct 2024 06:24:32 +0300	[thread overview]
Message-ID: <20241018032432.398821-1-parav@nvidia.com> (raw)

Field command-specific-data is a structure field. Annotate it
as a field so that generated pdf shows it accordingly.

Signed-off-by: Parav Pandit <parav@nvidia.com>
---
 device-types/net/description.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/device-types/net/description.tex b/device-types/net/description.tex
index b2a0d39..6950114 100644
--- a/device-types/net/description.tex
+++ b/device-types/net/description.tex
@@ -1217,7 +1217,7 @@ \subsubsection{Control Virtqueue}\label{sec:Device Types / Network Device / Devi
 #define VIRTIO_NET_ERR    1
 \end{lstlisting}
 
-The \field{class}, \field{command} and command-specific-data are set by the
+The \field{class}, \field{command} and \field{command-specific-data} are set by the
 driver, and the device sets the \field{ack} byte and optionally
 \field{command-specific-result}. There is little the driver can
 do except issue a diagnostic if \field{ack} is not VIRTIO_NET_OK.
-- 
2.34.1


             reply	other threads:[~2024-10-18  3:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18  3:24 Parav Pandit [this message]
2024-10-18  7:13 ` [PATCH] virtio-net: editorial: Annotate structure field Stefano Garzarella
2024-10-18 10:16   ` Parav Pandit
2024-10-18 12:30     ` Stefano Garzarella

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=20241018032432.398821-1-parav@nvidia.com \
    --to=parav@nvidia.com \
    --cc=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=mvaralar@redhat.com \
    --cc=shahafs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox