From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: 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>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH V9] virtio-transport: Add a section to define mandatory transport requirements
Date: Wed, 14 Aug 2024 14:20:57 +0200 [thread overview]
Message-ID: <ZryhKR2KooGiGmpn@fedora> (raw)
In-Reply-To: <20240814004203.ruvdkkeuuyhmbkk2@vireshk-i7>
On Wed, Aug 14, 2024 at 06:12:03AM +0530, Viresh Kumar wrote:
> Hi Matias,
>
> On 12-08-24, 12:55, Matias Ezequiel Vara Larsen wrote:
> > On Fri, Aug 09, 2024 at 03:52:28PM +0530, Viresh Kumar wrote:
> > > +Devices and drivers utilize various transport methods to facilitate
> > > +communication, such as PCI, MMIO, or Channel I/O. These transport
> > > +methods determine multiple aspects of the interaction between the device
> >
> > Maybe remove `multiple` here. I think it does not add much but I do not
> > have an strong opinion about this.
>
> What about 'various' instead of 'multiple' ? Or just drop the word ?
>
I would drop the word.
> > > +and the driver, including device discovery, capability exchange,
> > > +interrupt handling, and data transfer. For instance, in a host/guest
> > > +architecture, the host might expose a device to the guest via a virtual
> > > +PCI bus, and the guest would employ a PCI device driver to interface
> > > +with the device.
> > > +
> >
> > Maybe a verb different than `employ`? But I do not have an strong
> > opinion about this.
>
> 'use' ? Or something else ?
>
I think `use` is OK.
Matias
prev parent reply other threads:[~2024-08-14 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 10:22 [PATCH V9] virtio-transport: Add a section to define mandatory transport requirements Viresh Kumar
2024-08-12 10:55 ` Matias Ezequiel Vara Larsen
2024-08-14 0:42 ` Viresh Kumar
2024-08-14 12:20 ` Matias Ezequiel Vara Larsen [this message]
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=ZryhKR2KooGiGmpn@fedora \
--to=mvaralar@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=manos.pitsidianakis@linaro.org \
--cc=mst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox