From: Jeremy Katz <katzj@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: [Xen-changelog] Create /dev/xen/evtchn if it doesn't exist.
Date: Wed, 07 Sep 2005 18:31:45 -0400 [thread overview]
Message-ID: <1126132305.2474.126.camel@bree.local.net> (raw)
In-Reply-To: <431F5666.7070209@us.ibm.com>
On Wed, 2005-09-07 at 16:06 -0500, Anthony Liguori wrote:
> Another way to solve this problem is to just use "/dev/evtchn" as that
> is what will be created by udev.
>
> In fact, what does everyone think about just deprecating /dev/xen/evtchn
> and just using /dev/evtchn everywhere? I'll submit a patch if it's
> acceptable (including removing the places where we create /dev/xen/evtchn).
Sounds sane to me. If that's not done, then really, xenstored should
instead look in /proc to figure out the major/minor in case Linus ever
goes through with his threat to make all major/minors random ;-)
Jeremy
prev parent reply other threads:[~2005-09-07 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1ED6aa-0006WS-5H@xenbits.xensource.com>
2005-09-07 21:06 ` [Xen-changelog] Create /dev/xen/evtchn if it doesn't exist Anthony Liguori
2005-09-07 22:31 ` Jeremy Katz [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=1126132305.2474.126.camel@bree.local.net \
--to=katzj@redhat.com \
--cc=aliguori@us.ibm.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.