From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH] xennet_get_drvinfo() Date: Thu, 25 Nov 2010 11:15:22 -0800 Message-ID: <4CEEB5CA.6050704@goop.org> References: <4CDC3003.5040306@redhat.com> <1289501456.20667.7.camel@localhost.localdomain> <4CED7792.1090600@goop.org> <4CED79E4.4030608@redhat.com> <4CED7C03.6000803@goop.org> <1290680231.5514.2239.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1290680231.5514.2239.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , Laszlo Ersek List-Id: xen-devel@lists.xenproject.org On 11/25/2010 02:17 AM, Ian Campbell wrote: > On Wed, 2010-11-24 at 20:56 +0000, Jeremy Fitzhardinge wrote: >>> The fallback does cover the functionality ("driver: vif"), but >>> "driver: xen-netfront" seems to be nicer, because that matches the >>> module (driver) name. >> Hm. Well, perhaps we should change the driver name? We can keep >> "vif" as an alias. > Whatever we do we shouldn't deliberately cause the xen.git 2.6.32 branch > to deviate from what upstream does, if we think this field needs > renaming lets do it on linux-netdev and backport the result. Yes, exactly. I backported Ben's change so that .32 would be more like later kernels; if the device name is useless (which it is), then we should change it everywhere. J