From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Bastian Blank <waldi@debian.org>,
xen-devel@lists.xensource.com,
Jeremy Fitzhardinge <jeremy@goop.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] Fix name of Xen event-channel device
Date: Thu, 27 May 2010 12:26:56 -0400 [thread overview]
Message-ID: <20100527162656.GA6190@phenom.dumpdata.com> (raw)
In-Reply-To: <20100527150251.GD6040@wavehammer.waldi.eu.org>
On Thu, May 27, 2010 at 05:02:51PM +0200, Bastian Blank wrote:
> The Xen event-channel device is named evtchn in the kernel but always
> used as /dev/xen/evtchn in userspace. This patch fixes the name.
Hey Bastian,
Is this related to this bug:
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612 ?
I saw it in some reference to the evtchn but wasn't sure if this is the
same.
>
> Signed-off-by: Bastian Blank <waldi@debian.org>
>
> diff --git a/drivers/xen/evtchn.c b/drivers/xen/evtchn.c
> index 66e185c..89cd743 100644
> --- a/drivers/xen/evtchn.c
> +++ b/drivers/xen/evtchn.c
> @@ -471,7 +471,7 @@ static const struct file_operations evtchn_fops = {
>
> static struct miscdevice evtchn_miscdev = {
> .minor = MISC_DYNAMIC_MINOR,
> - .name = "evtchn",
> + .name = "xen/evtchn",
> .fops = &evtchn_fops,
> };
> static int __init evtchn_init(void)
> --
> Yes, it is written. Good shall always destroy evil.
> -- Sirah the Yang, "The Omega Glory", stardate unknown
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-27 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 10:51 Name of event-channel and other devices vs. udev Bastian Blank
2010-05-27 0:08 ` Jeremy Fitzhardinge
2010-05-27 7:35 ` Bastian Blank
2010-05-27 14:31 ` Bastian Blank
2010-05-27 15:02 ` [PATCH] Fix name of Xen event-channel device Bastian Blank
2010-05-27 16:26 ` Konrad Rzeszutek Wilk [this message]
2010-05-27 16:50 ` Michael Tokarev
2010-05-27 17:13 ` Bastian Blank
2010-05-28 13:24 ` Kay Sievers
2010-05-28 13:41 ` Michael Tokarev
2010-05-28 23:20 ` Jeremy Fitzhardinge
2010-05-27 22:05 ` Name of event-channel and other devices vs. udev Jeremy Fitzhardinge
2010-05-27 22:26 ` Bastian Blank
2010-05-27 22:37 ` Jeremy Fitzhardinge
2010-05-27 22:58 ` Bastian Blank
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=20100527162656.GA6190@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=waldi@debian.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).