This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [PATCH 3/3] xen: rename pciback module to xen-pciback.

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 3/3] xen: rename pciback module to xen-pciback.
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Thu, 03 Dec 2009 14:18:35 -0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Thu, 03 Dec 2009 14:18:58 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1259878468.31045.139.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1259877380-32275-1-git-send-email-ian.campbell@xxxxxxxxxx> <1259877380-32275-4-git-send-email-ian.campbell@xxxxxxxxxx> <20091203220237.GA21885@xxxxxxxxxxxxxxxxxxx> <1259878468.31045.139.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20091125 Fedora/3.0-3.12.rc1.fc12 Lightning/1.0pre Thunderbird/3.0
On 12/03/09 14:14, Ian Campbell wrote:
Ah, it never even occurred to me that such a thing would be necessary.

I think (but I should check) that the sysfs name will remain pciback
since it comes from the .name in struct xenbus_driver. I'm not sure if
it is confusing or not to have the module name be different to the
driver name nor how common it is.

The driver name is a bit of an ABI for hotplug, etc, anyway, so having the Xen tools depend on that name isn't very odd. And while it is best if the module matches the driver name, it's not uncommon for it to mismatch - and we've been doing it for ages anyway (xen_netfront is called "vif" and aliased "xen:vif" and "xennet").


Xen-devel mailing list