Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Heng Qi <hengqi@linux.alibaba.com>
To: Cornelia Huck <cohuck@redhat.com>, Jason Wang <jasowang@redhat.com>
Cc: virtio-comment@lists.oasis-open.org,
	virtio-dev@lists.oasis-open.org,
	"Michael S . Tsirkin" <mst@redhat.com>,
	Yuri Benditovich <yuri.benditovich@daynix.com>,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [virtio-comment] Re: [virtio-dev] Re: [PATCH v3] virtio_net: support inner header hash
Date: Wed, 14 Dec 2022 17:39:04 +0800	[thread overview]
Message-ID: <bc6d4fa8-5ece-35ca-2ac4-a7b90a4a7bfb@linux.alibaba.com> (raw)
In-Reply-To: <875yeebaed.fsf@redhat.com>



在 2022/12/14 下午5:30, Cornelia Huck 写道:
> On Wed, Dec 14 2022, Heng Qi <hengqi@linux.alibaba.com> wrote:
>
>> 在 2022/12/14 下午5:12, Jason Wang 写道:
>>> On Wed, Dec 14, 2022 at 5:01 PM Heng Qi <hengqi@linux.alibaba.com> wrote:
>>>> On Fri, Dec 09, 2022 at 02:09:18PM +0800, Heng Qi wrote:
>>>>> Do you have any comments on this new version?
>>>>>
>>>> If the reviewers do not have more comments on
>>> I plan to review this no later than the end of this week.
>> Okay, I see.
>>
>> @Cornelia Huck, Although I have submitted the voting issue, please wait
>> for a while for @Jason Wang to review, thank you.
> Ack, will do.
>
> (I'm not sure if I'll start voting that close to the end of the year
> anyway; many people in western countries will be offline until early
> January soon.)

Ok, I got it.

Thanks.

>
> 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/


  reply	other threads:[~2022-12-14  9:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05  6:36 [PATCH v3] virtio_net: support inner header hash Heng Qi
2022-12-09  6:09 ` Heng Qi
2022-12-14  9:01   ` [virtio-dev] " Heng Qi
2022-12-14  9:12     ` Jason Wang
2022-12-14  9:16       ` Heng Qi
2022-12-14  9:30         ` [virtio-comment] " Cornelia Huck
2022-12-14  9:39           ` Heng Qi [this message]
2022-12-15  7:46           ` Michael S. Tsirkin
2022-12-16  6:33 ` Jason Wang
2022-12-16 10:14   ` Heng Qi
2022-12-20 14:27     ` [virtio-comment] " Heng Qi
2022-12-21  3:15       ` Jason Wang
2022-12-21  6:16         ` Heng Qi
2022-12-16 12:49 ` Michael S. Tsirkin
2022-12-19  2:52   ` [virtio-comment] " Heng Qi

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=bc6d4fa8-5ece-35ca-2ac4-a7b90a4a7bfb@linux.alibaba.com \
    --to=hengqi@linux.alibaba.com \
    --cc=cohuck@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=xuanzhuo@linux.alibaba.com \
    --cc=yuri.benditovich@daynix.com \
    /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