From: "Michael S. Tsirkin" <mst@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Parav Pandit" <parav@nvidia.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"stratos-dev@op-lists.linaro.org"
<stratos-dev@op-lists.linaro.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>
Subject: Re: [PATCH V5] virtio-transport: Clarify requirements
Date: Fri, 21 Jun 2024 05:39:40 -0400 [thread overview]
Message-ID: <20240621053854-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240613093203.24hcx7euw6txy3zs@vireshk-i7>
On Thu, Jun 13, 2024 at 03:02:03PM +0530, Viresh Kumar wrote:
> On 11-06-24, 14:11, Viresh Kumar wrote:
> > On 11-06-24, 07:41, Parav Pandit wrote:
> > > Got it.
> > > I agree to Michael's suggestion "I feel a non-normative section is enough for this."
> > > So following his guidance, we should remove it from the requirements and have this as,
> > >
> > > "implementation guide" or appendix section and it also looks good without the key wards too.
> > >
> > > Otherwise, this requirement section becomes the example of how not to write normative in a normative section.
> > > (and we want to avoid future such examples).
> >
> > I am okay with whatever Cornelia and Michael finalize on this.
>
> Michael, Cornelia: Any decision on this ?
On what?
> --
> viresh
next prev parent reply other threads:[~2024-06-21 9:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 5:35 [PATCH V5] virtio-transport: Clarify requirements Viresh Kumar
2024-06-11 6:10 ` Parav Pandit
2024-06-11 6:58 ` Viresh Kumar
2024-06-11 7:41 ` Parav Pandit
2024-06-11 8:41 ` Viresh Kumar
2024-06-11 8:54 ` Parav Pandit
2024-06-13 9:32 ` Viresh Kumar
2024-06-21 8:05 ` Viresh Kumar
2024-06-21 9:39 ` Michael S. Tsirkin [this message]
2024-06-21 9:43 ` Viresh Kumar
2024-06-21 10:08 ` Michael S. Tsirkin
2024-06-11 15:28 ` Cornelia Huck
2024-06-11 17:40 ` Parav Pandit
2024-06-12 7:19 ` Michael S. Tsirkin
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=20240621053854-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=parav@nvidia.com \
--cc=stratos-dev@op-lists.linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--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