From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH 3/3] xen: rename pciback module to xen-pciback.
Date: Thu, 03 Dec 2009 14:18:35 -0800 [thread overview]
Message-ID: <4B18393B.4050700@goop.org> (raw)
In-Reply-To: <1259878468.31045.139.camel@localhost.localdomain>
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").
J
prev parent reply other threads:[~2009-12-03 22:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 21:56 Rename backend modules to be less generic ian.campbell
2009-12-03 21:56 ` [PATCH 1/3] xen: rename blkbk module xen-blkback ian.campbell
2009-12-03 21:56 ` [PATCH 2/3] xen: rename netbk module xen-netback ian.campbell
2009-12-03 21:56 ` [PATCH 3/3] xen: rename pciback module to xen-pciback ian.campbell
2009-12-03 22:02 ` Konrad Rzeszutek Wilk
2009-12-03 22:08 ` Jeremy Fitzhardinge
2009-12-03 22:20 ` Konrad Rzeszutek Wilk
2009-12-03 22:14 ` Ian Campbell
2009-12-03 22:18 ` Jeremy Fitzhardinge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B18393B.4050700@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.