From: "Michael S. Tsirkin" <mst@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Stefano Garzarella" <sgarzare@redhat.com>,
virtio-comment@lists.linux.dev,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Cornelia Huck" <cohuck@redhat.com>,
"Parav Pandit" <parav@nvidia.com>,
"Matias Ezequiel Vara Larsen" <mvaralar@redhat.com>
Subject: Re: [PATCH V7] virtio-transport: Add a new section to clarify transport requirements
Date: Thu, 11 Jul 2024 07:07:23 -0400 [thread overview]
Message-ID: <20240711070635-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240711092332.uf5n4sbzke52tf52@vireshk-i7>
On Thu, Jul 11, 2024 at 02:53:32PM +0530, Viresh Kumar wrote:
> On 11-07-24, 10:41, Stefano Garzarella wrote:
> > On Thu, Jul 11, 2024 at 01:18:18PM GMT, Viresh Kumar wrote:
> > > +A transport provides a mechanism for the driver to discover the device.
> >
> > I agree that this would be desirable, but for example IIUC the MMIO
> > transport does not provide this, in fact we have to specify to the kernel
> > the address where to find the devices.
> >
> > Should we put it more as something desirable but not required?
>
> What about:
>
> A transport may provide a mechanism for the driver to discover the device.
>
> But I thought I am required to remove all occurrences of
> should/must/may and use direct speech. Maybe "may" is still fine ? :)
Nope, but "can" is fine.
You are not supposed to just mechanically remove text, rephrase so
it still makes sense.
> > Having said that I don't know whether to use different words or split
> > "Transport Requirements" into 2 sub sections "Required Requirements" and
> > "Optional Requirements".
>
> --
> viresh
next prev parent reply other threads:[~2024-07-11 11:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 7:48 [PATCH V7] virtio-transport: Add a new section to clarify transport requirements Viresh Kumar
2024-07-11 8:24 ` Cornelia Huck
2024-07-11 9:05 ` Viresh Kumar
2024-07-11 10:59 ` Michael S. Tsirkin
2024-07-11 8:41 ` Stefano Garzarella
2024-07-11 9:23 ` Viresh Kumar
2024-07-11 11:07 ` Michael S. Tsirkin [this message]
2024-07-11 11:10 ` Michael S. Tsirkin
2024-07-11 11:46 ` Cornelia Huck
2024-07-11 11:51 ` Michael S. Tsirkin
2024-07-11 11:59 ` Cornelia Huck
2024-07-11 14:30 ` Michael S. Tsirkin
2024-07-11 14:44 ` Cornelia Huck
2024-07-11 14:49 ` Michael S. Tsirkin
2024-07-11 14:59 ` Cornelia Huck
2024-07-24 10:45 ` Viresh Kumar
2024-07-24 11:05 ` Michael S. Tsirkin
2024-07-25 9:15 ` Viresh Kumar
2024-07-25 9:28 ` Michael S. Tsirkin
2024-07-25 10:55 ` Viresh Kumar
2024-07-25 12:24 ` Michael S. Tsirkin
2024-07-29 3:36 ` Viresh Kumar
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=20240711070635-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=mvaralar@redhat.com \
--cc=parav@nvidia.com \
--cc=sgarzare@redhat.com \
--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 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.