From: Bastian Blank <waldi@debian.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xc: deal with xen/evtchn and xen/gntdev device names
Date: Tue, 1 Jun 2010 10:17:07 +0200 [thread overview]
Message-ID: <20100601081707.GA24351@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <1275379012.24218.20337.camel@zakaz.uk.xensource.com>
On Tue, Jun 01, 2010 at 08:56:52AM +0100, Ian Campbell wrote:
> Does any of this logic really belong in libxc in the first place?
No.
> Can we not just rip it all out and make it the distro/platform's
> responsibility to ensure these devices exist and are correct?
Thats what I forced in Debian right now.
> Perhaps
> that might involve shipping some default/example udev rules instead.
With the fixed kernel this needs no rules. Even with devtmpfs (some
people call it devfs version 2) and no udev it will work then.
Bastian
--
Vulcans believe peace should not depend on force.
-- Amanda, "Journey to Babel", stardate 3842.3
next prev parent reply other threads:[~2010-06-01 8:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 1:08 [PATCH] xc: deal with xen/evtchn and xen/gntdev device names Jeremy Fitzhardinge
2010-05-29 6:53 ` Bastian Blank
2010-06-01 7:56 ` Ian Campbell
2010-06-01 8:17 ` Bastian Blank [this message]
2010-06-01 16:35 ` Jeremy Fitzhardinge
2010-06-02 9:29 ` Ian Campbell
2010-06-02 16:09 ` Jeremy Fitzhardinge
2010-06-03 8:31 ` Ian Campbell
2010-06-03 19:32 ` Jeremy Fitzhardinge
2010-06-04 9:55 ` Ian Campbell
2010-06-04 10:01 ` Keir Fraser
2010-06-04 15:27 ` Dan Magenheimer
2010-06-04 15:31 ` Ian Campbell
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=20100601081707.GA24351@wavehammer.waldi.eu.org \
--to=waldi@debian.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).