From: Cornelia Huck <cohuck@redhat.com>
To: Yuri Benditovich <yuri.benditovich@daynix.com>
Cc: Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: VIRTIO_NET_HDR_F_RSC_INFO in virtio-net vs headers update
Date: Mon, 27 Apr 2020 12:38:33 +0200 [thread overview]
Message-ID: <20200427123833.52ef442a.cohuck@redhat.com> (raw)
In-Reply-To: <CAOEp5OdSnxMO-BY+8NLwntjpr3CGvfh0ECHHB0w7PVAZ7OArog@mail.gmail.com>
On Mon, 27 Apr 2020 12:52:26 +0300
Yuri Benditovich <yuri.benditovich@daynix.com> wrote:
> I'd suggest to do the single change in virtio-net.c with RSC definitions
> from updated linux headers.
> I can send respective patch if you want
Hm, I already sent something out before I saw your mail... can you
please look at that one?
prev parent reply other threads:[~2020-04-27 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 7:33 VIRTIO_NET_HDR_F_RSC_INFO in virtio-net vs headers update Cornelia Huck
2020-04-27 8:41 ` Jason Wang
2020-04-27 9:10 ` Cornelia Huck
2020-04-27 9:18 ` Michael S. Tsirkin
2020-04-27 9:52 ` Yuri Benditovich
2020-04-27 10:38 ` 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=20200427123833.52ef442a.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--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;
as well as URLs for NNTP newsgroup(s).