From: Cornelia Huck <cohuck@redhat.com>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: virtio-comment@lists.oasis-open.org,
Rabeeh Khoury <rabeeh@solid-run.com>
Subject: Re: [virtio-comment] [PATCH v5] Introduction of Virtio Network device notifications coalescing feature.
Date: Tue, 07 Jun 2022 13:08:33 +0200 [thread overview]
Message-ID: <878rq8buj2.fsf@redhat.com> (raw)
In-Reply-To: <CAJs=3_CNBusJiSvey5JFyNkFecta2ARA+CEbv7aApK6YbxKE5Q@mail.gmail.com>
On Tue, Jun 07 2022, Alvaro Karsz <alvaro.karsz@solid-run.com> wrote:
> Thanks for the reply.
>
>> s/if/if it/
>
> I'm not sure I understand what you mean here.
The sentence was missing an "it": "...if it was not able to..."
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
prev parent reply other threads:[~2022-06-07 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 6:44 [virtio-comment] [PATCH v5] Introduction of Virtio Network device notifications coalescing feature Alvaro Karsz
2022-06-06 15:29 ` [virtio-comment] " Alvaro Karsz
2022-06-07 10:45 ` [virtio-comment] " Cornelia Huck
2022-06-07 10:51 ` Alvaro Karsz
2022-06-07 11:08 ` Cornelia Huck [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=878rq8buj2.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=rabeeh@solid-run.com \
--cc=virtio-comment@lists.oasis-open.org \
/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