From: Michael Tokarev Subject: Re: [PATCH] Fix name of Xen event-channel device Date: Thu, 27 May 2010 20:50:39 +0400 Message-ID: <4BFEA2DF.8080006@msgid.tls.msk.ru> References: <20100526105144.GA28280@wavehammer.waldi.eu.org> <20100527073512.GA17135@wavehammer.waldi.eu.org> <20100527143104.GB6040@wavehammer.waldi.eu.org> <20100527150251.GD6040@wavehammer.waldi.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100527150251.GD6040@wavehammer.waldi.eu.org> Sender: linux-kernel-owner@vger.kernel.org To: Bastian Blank , xen-devel@lists.xensource.com, Jeremy Fitzhardinge , linux-kernel@vger.kernel.org List-Id: xen-devel@lists.xenproject.org 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. > > Signed-off-by: Bastian Blank > > 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", Um. Will existing userspace - esp. udev rules - continue to work after this change? Also, how about other xen-related devices which are moved to /dev/xen in that same udev rules? Thanks! /mjt