From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Conole Subject: Re: [PATCH] virtio-net: Update the mtu code to match virtio spec Date: Tue, 25 Oct 2016 16:06:41 -0400 Message-ID: References: <1477413335-17296-1-git-send-email-aconole@redhat.com> Mime-Version: 1.0 Content-Type: text/plain Cc: virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, "Michael S. Tsirkin" , Jarod Wilson To: netdev@vger.kernel.org Return-path: In-Reply-To: <1477413335-17296-1-git-send-email-aconole@redhat.com> (Aaron Conole's message of "Tue, 25 Oct 2016 12:35:35 -0400") Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org > From: Aaron Conole > > 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" > Cc: Jarod Wilson > Signed-off-by: Aaron Conole > --- 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? -Aaron