From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xen: rename gntdev and evtdev modules to be less generic
Date: Thu, 10 Dec 2009 22:50:04 +0000 [thread overview]
Message-ID: <1260485404.2367.4.camel@localhost.localdomain> (raw)
In-Reply-To: <4B2163CC.7040005@goop.org>
On Thu, 2009-12-10 at 21:10 +0000, Jeremy Fitzhardinge wrote:
> On 12/06/09 03:07, Ian Campbell wrote:
> > Also allow gntdev to be built as a module.
> >
>
> I think this breaks auto-loading of evtchn when its a module;
It never occurred to me that autoloading would work at all for this
driver, I always just load the module explicitly by listing
in /etc/modules. What triggers (or is supposed to trigger) autoloading?
> I suspect xen-backend.rules needs updating to match.
That is only to do with making sure the node gets called /dev/xen/evtchn
(presumably it would be /dev/evtchn, now /dev/xen-evtchn, otherwise).
This works for me.
Ian.
next prev parent reply other threads:[~2009-12-10 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 11:07 [PATCH] xen: rename gntdev and evtdev modules to be less generic Ian Campbell
2009-12-08 0:21 ` Jeremy Fitzhardinge
2009-12-08 0:29 ` Re: [PATCH] xen: rename gntdev and evtdev modules to beless generic James Harper
2009-12-08 0:47 ` Jeremy Fitzhardinge
2009-12-10 21:10 ` [PATCH] xen: rename gntdev and evtdev modules to be less generic Jeremy Fitzhardinge
2009-12-10 22:50 ` Ian Campbell [this message]
2009-12-10 23:25 ` Jeremy Fitzhardinge
2009-12-11 8:56 ` Ian Campbell
2009-12-11 11:50 ` Ian Campbell
2009-12-11 13:22 ` Gerd Hoffmann
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=1260485404.2367.4.camel@localhost.localdomain \
--to=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--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.