From: Cornelia Huck <cohuck@redhat.com>
To: Peter Hilber <quic_philber@quicinc.com>, virtio-comment@lists.linux.dev
Cc: Parav Pandit <parav@nvidia.com>, Jason Wang <jasowang@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
"Ridoux, Julien" <ridouxj@amazon.com>,
Trilok Soni <quic_tsoni@quicinc.com>,
Matias Ezequiel Vara Larsen <mvaralar@redhat.com>,
Peter Hilber <quic_philber@quicinc.com>
Subject: Re: [PATCH v8 2/4] virtio-rtc: Add initial normative statements
Date: Tue, 15 Apr 2025 15:46:03 +0200 [thread overview]
Message-ID: <87mschsfl0.fsf@redhat.com> (raw)
In-Reply-To: <20250306095112.1293-3-quic_philber@quicinc.com>
On Thu, Mar 06 2025, Peter Hilber <quic_philber@quicinc.com> wrote:
> Add the normative statements for the initial device specification.
>
> Signed-off-by: Peter Hilber <quic_philber@quicinc.com>
(...)
> diff --git a/device-types/rtc/description.tex b/device-types/rtc/description.tex
> index 5d8cf91a6991..f2a3907de511 100644
> --- a/device-types/rtc/description.tex
> +++ b/device-types/rtc/description.tex
> @@ -73,7 +73,7 @@ \subsection{Device Operation}\label{sec:Device Types / RTC Device / Device Opera
> VIRTIO_RTC_S_EOPNOTSUPP indicates that the device could not execute the
> specific request due to an implementation limitation. The device also
> returns status VIRTIO_RTC_S_EOPNOTSUPP for requests with unknown values
> -in the fields \field{msg_type} or \field{hw_counter}.
> +in the \field{msg_type} or \field{hw_counter} fields.
Looks like some hunks with wording changes ended up in the wrong patch?
(A couple more of those in the remainder of this patch.)
next prev parent reply other threads:[~2025-04-15 13:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 9:51 [PATCH v8 0/4] virtio-rtc: Add device specification Peter Hilber
2025-03-06 9:51 ` [PATCH v8 1/4] virtio-rtc: Add initial " Peter Hilber
2025-04-15 13:43 ` Cornelia Huck
2025-04-15 14:17 ` Peter Hilber
2025-04-15 14:38 ` Cornelia Huck
2025-04-15 15:04 ` Matias Ezequiel Vara Larsen
2025-04-17 14:42 ` Peter Hilber
2025-04-16 15:33 ` Michael S. Tsirkin
2025-04-17 15:14 ` Peter Hilber
2025-04-17 16:14 ` Michael S. Tsirkin
2025-04-22 10:47 ` Peter Hilber
2025-04-22 10:52 ` Michael S. Tsirkin
2025-03-06 9:51 ` [PATCH v8 2/4] virtio-rtc: Add initial normative statements Peter Hilber
2025-04-15 13:46 ` Cornelia Huck [this message]
2025-04-15 14:28 ` Peter Hilber
2025-04-15 16:03 ` Matias Ezequiel Vara Larsen
2025-04-17 14:58 ` Peter Hilber
2025-04-16 15:42 ` Michael S. Tsirkin
2025-04-17 15:15 ` Peter Hilber
2025-03-06 9:51 ` [PATCH v8 3/4] virtio-rtc: Add alarm feature Peter Hilber
2025-04-16 8:17 ` Matias Ezequiel Vara Larsen
2025-04-17 15:04 ` Peter Hilber
2025-05-06 15:19 ` Peter Hilber
2025-03-06 9:51 ` [PATCH v8 4/4] virtio-rtc: Add normative statements for " Peter Hilber
2025-04-16 12:14 ` Matias Ezequiel Vara Larsen
2025-04-17 15:07 ` Peter Hilber
2025-04-15 12:46 ` [PATCH v8 0/4] virtio-rtc: Add device specification Peter Hilber
2025-04-16 13:02 ` Matias Ezequiel Vara Larsen
2025-04-16 14:44 ` Peter Hilber
2025-04-16 14:59 ` Matias Ezequiel Vara Larsen
2025-04-16 15:43 ` Michael S. Tsirkin
2025-04-17 15:08 ` Peter Hilber
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=87mschsfl0.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jasowang@redhat.com \
--cc=mvaralar@redhat.com \
--cc=parav@nvidia.com \
--cc=quic_philber@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=ridouxj@amazon.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.