[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f7tpomo5gph.fsf@redhat.com>
Date: Tue, 25 Oct 2016 16:14:34 -0400
From: Aaron Conole <aconole@...hat.com>
To: netdev@...r.kernel.org
Cc: virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org,
"Michael S. Tsirkin" <mst@...hat.com>,
Jarod Wilson <jarod@...hat.com>
Subject: Re: [PATCH] virtio-net: Update the mtu code to match virtio spec
Aaron Conole <aconole@...hat.com> writes:
>> From: Aaron Conole <aconole@...heb.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@...hat.com>
>> Cc: Jarod Wilson <jarod@...hat.com>
>> Signed-off-by: Aaron Conole <aconole@...hat.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.
Powered by blists - more mailing lists