From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756126AbcJYUOi (ORCPT ); Tue, 25 Oct 2016 16:14:38 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52552 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750806AbcJYUOg (ORCPT ); Tue, 25 Oct 2016 16:14:36 -0400 From: Aaron Conole To: netdev@vger.kernel.org Cc: virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, "Michael S. Tsirkin" , Jarod Wilson Subject: Re: [PATCH] virtio-net: Update the mtu code to match virtio spec References: <1477413335-17296-1-git-send-email-aconole@redhat.com> Date: Tue, 25 Oct 2016 16:14:34 -0400 In-Reply-To: (Aaron Conole's message of "Tue, 25 Oct 2016 16:06:41 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Tue, 25 Oct 2016 20:14:36 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Aaron Conole writes: >> 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? I answered my own question. Sorry for the noise.