From: Aaron Conole <aconole@redhat.com>
To: netdev@vger.kernel.org
Cc: virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>,
Jarod Wilson <jarod@redhat.com>
Subject: Re: [PATCH] virtio-net: Update the mtu code to match virtio spec
Date: Tue, 25 Oct 2016 16:14:34 -0400 [thread overview]
Message-ID: <f7tpomo5gph.fsf@redhat.com> (raw)
In-Reply-To: <f7ta8ds9ory.fsf@redhat.com> (Aaron Conole's message of "Tue, 25 Oct 2016 16:06:41 -0400")
Aaron Conole <aconole@redhat.com> writes:
>> From: Aaron Conole <aconole@bytheb.org>
>>
>> The virtio committee recently ratified a change, VIRTIO-152, which
>> defines the mtu field to be 'max' MTU, not simply desired MTU.
>>
>> This commit brings the virtio-net device in compliance with VIRTIO-152.
>>
>> Additionally, drop the max_mtu branch - it cannot be taken since the u16
>> returned by virtio_cread16 will never exceed the initial value of
>> max_mtu.
>>
>> Cc: "Michael S. Tsirkin" <mst@redhat.com>
>> Cc: Jarod Wilson <jarod@redhat.com>
>> Signed-off-by: Aaron Conole <aconole@redhat.com>
>> ---
>
> Sorry about the subject line, David. This is targetted at net-next, and
> it appears my from was mangled. Would you like me to resubmit with
> these details corrected?
I answered my own question. Sorry for the noise.
prev parent reply other threads:[~2016-10-25 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 16:35 [PATCH] virtio-net: Update the mtu code to match virtio spec Aaron Conole
2016-10-25 16:35 ` Aaron Conole
2016-10-25 16:41 ` Michael S. Tsirkin
2016-10-25 16:41 ` Michael S. Tsirkin
2016-10-25 17:09 ` Jarod Wilson
2016-10-25 17:09 ` Jarod Wilson
2016-10-25 20:06 ` Aaron Conole
2016-10-25 20:06 ` Aaron Conole
2016-10-25 20:14 ` Aaron Conole
2016-10-25 20:14 ` Aaron Conole [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=f7tpomo5gph.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=jarod@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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 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.