public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Bastian Blank <waldi@debian.org>,
	xen-devel@lists.xensource.com,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix name of Xen event-channel device
Date: Thu, 27 May 2010 20:50:39 +0400	[thread overview]
Message-ID: <4BFEA2DF.8080006@msgid.tls.msk.ru> (raw)
In-Reply-To: <20100527150251.GD6040@wavehammer.waldi.eu.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 <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",

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

  parent reply	other threads:[~2010-05-27 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100526105144.GA28280@wavehammer.waldi.eu.org>
     [not found] ` <20100527073512.GA17135@wavehammer.waldi.eu.org>
     [not found]   ` <20100527143104.GB6040@wavehammer.waldi.eu.org>
2010-05-27 15:02     ` [PATCH] Fix name of Xen event-channel device Bastian Blank
2010-05-27 16:26       ` [Xen-devel] " Konrad Rzeszutek Wilk
2010-05-27 16:50       ` Michael Tokarev [this message]
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

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=4BFEA2DF.8080006@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --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