From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Hilber <peter.hilber@opensynergy.com>
Cc: virtio-comment@lists.linux.dev, Cornelia Huck <cohuck@redhat.com>,
Parav Pandit <parav@nvidia.com>
Subject: Re: [virtio-comment] [RFC PATCH v3 0/4] virtio-rtc: Add device specification
Date: Thu, 25 Jul 2024 00:53:42 -0400 [thread overview]
Message-ID: <20240725005322-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20231218064253.9734-1-peter.hilber@opensynergy.com>
On Mon, Dec 18, 2023 at 07:42:49AM +0100, Peter Hilber wrote:
> This iteration of the virtio-rtc RFC spec
>
> - addresses the comments from Parav (patch 1),
>
> - separates the normative statements into a dedicated patch (patch 2), and
>
> - adds an optional alarm feature (patch 3-4).
>
> Summary
> -------
>
> The RTC (Real Time Clock) device provides information about current
> time. The device can provide different clocks, e.g. for the UTC or TAI
> time standards, or for physical time elapsed since some past epoch. The
> driver can read the clocks with simple or more accurate methods.
> Optionally, the driver can set an alarm.
What is the status here?
--
MST
next prev parent reply other threads:[~2024-07-25 4:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 6:42 [virtio-comment] [RFC PATCH v3 0/4] virtio-rtc: Add device specification Peter Hilber
2023-12-18 6:42 ` [virtio-comment] [RFC PATCH v3 1/4] virtio-rtc: Add initial " Peter Hilber
2024-01-20 10:07 ` [virtio-comment] " Parav Pandit
2024-01-24 15:39 ` [virtio-comment] " Peter Hilber
2024-01-28 6:15 ` [virtio-comment] " Parav Pandit
2024-02-08 11:57 ` Peter Hilber
2024-02-09 11:43 ` Cornelia Huck
2023-12-18 6:42 ` [virtio-comment] [RFC PATCH v3 2/4] virtio-rtc: Add initial normative statements Peter Hilber
2023-12-18 6:42 ` [virtio-comment] [RFC PATCH v3 3/4] virtio-rtc: Add alarm feature Peter Hilber
2023-12-22 18:57 ` Cornelia Huck
2023-12-25 4:18 ` Jason Wang
2024-01-11 11:43 ` Peter Hilber
2024-01-11 11:43 ` Peter Hilber
2024-01-15 15:54 ` Cornelia Huck
2024-01-16 11:06 ` Peter Hilber
2024-01-20 10:16 ` [virtio-comment] " Parav Pandit
2024-01-24 15:40 ` [virtio-comment] " Peter Hilber
2024-01-28 6:30 ` [virtio-comment] " Parav Pandit
2024-01-29 16:51 ` Cornelia Huck
2024-02-01 5:53 ` Parav Pandit
2023-12-18 6:42 ` [virtio-comment] [RFC PATCH v3 4/4] virtio-rtc: Add normative statements for " Peter Hilber
2024-07-25 4:53 ` Michael S. Tsirkin [this message]
2024-07-25 8:32 ` [virtio-comment] [RFC PATCH v3 0/4] virtio-rtc: Add device specification David Woodhouse
2024-08-09 12:53 ` 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=20240725005322-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=parav@nvidia.com \
--cc=peter.hilber@opensynergy.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.