From: Cornelia Huck <cohuck@redhat.com>
To: "Zhu, Lingshan" <lingshan.zhu@amd.com>,
Parav Pandit <parav@nvidia.com>,
"mst@redhat.com" <mst@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>
Cc: "virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>,
"Ray.Huang@amd.com" <Ray.Huang@amd.com>
Subject: Re: [PATCH v3 3/3] virtio: introduce SUSPEND and RESUME feature
Date: Fri, 27 Jun 2025 10:27:47 +0200 [thread overview]
Message-ID: <87ms9th9mk.fsf@redhat.com> (raw)
In-Reply-To: <e0115f0c-951f-4a76-8795-d34b6f088467@amd.com>
On Fri, Jun 27 2025, "Zhu, Lingshan" <lingshan.zhu@amd.com> wrote:
> On 6/26/2025 11:42 PM, Cornelia Huck wrote:
>
>> The intention is to use them in normative statements only, so that
>> implementers have clear guidelines on the requirements. The legacy
>> sections are arguably a special case (for implementers who want to
>> support legacy implementations.) I don't think we want the all-caps key
>> words leaking into other sections (any more than what might have
>> happened already.)
>
> so this is a new requirement, we need to document these guidance
Not new, but not documented, either. I see that Parav is already
tackling the latter part (thanks!)
next prev parent reply other threads:[~2025-06-27 8:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 8:36 [PATCH v3 0/3] Implement virtio SUSPEND and RESUME feature Zhu Lingshan
2025-06-23 8:36 ` [PATCH v3 1/3] virtio: re-order device status bits Zhu Lingshan
2025-06-26 11:39 ` Parav Pandit
2025-06-23 8:36 ` [PATCH v3 2/3] virtio: document feature bit 42 Zhu Lingshan
2025-06-26 11:45 ` Parav Pandit
2025-06-26 13:06 ` Zhu, Lingshan
2025-06-23 8:36 ` [PATCH v3 3/3] virtio: introduce SUSPEND and RESUME feature Zhu Lingshan
2025-06-26 11:59 ` Parav Pandit
2025-06-26 13:25 ` Zhu, Lingshan
2025-06-26 13:40 ` Parav Pandit
2025-06-27 1:57 ` Zhu, Lingshan
2025-06-26 15:42 ` Cornelia Huck
2025-06-26 16:01 ` Parav Pandit
2025-06-27 1:46 ` Zhu, Lingshan
2025-06-27 8:27 ` Cornelia Huck [this message]
2025-06-27 11:47 ` Michael S. Tsirkin
2025-06-27 4: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=87ms9th9mk.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=Ray.Huang@amd.com \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@amd.com \
--cc=mst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox