xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Bastian Blank <waldi@debian.org>,
	Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] xc: deal with xen/evtchn and xen/gntdev device names
Date: Fri, 4 Jun 2010 11:01:51 +0100	[thread overview]
Message-ID: <C82E8D9F.16AB3%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <1275645308.24218.34883.camel@zakaz.uk.xensource.com>

On 04/06/2010 10:55, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:

>>> If so I think that's an argument for propagating the removal of this
>>> functionality into stable trees sooner rather than later rather than
>>> papering over the craziness for even longer.
> 
> Keir has applied my patch so I'll keep an eye out for fallout and
> suggest it for backporting to the stable branch when it looks like we've
> gotten away with it.

Any fallout should be dealt with by getting users to set up proper udev
rules, I'm sure. I backported to 4.0 for 4.0.1, so I have confidence. ;-)

 -- Keir

  reply	other threads:[~2010-06-04 10:01 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
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 [this message]
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=C82E8D9F.16AB3%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=jeremy@goop.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).