All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bastian Blank <waldi@debian.org>,
	Michael Tokarev <mjt@tls.msk.ru>,
	xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix name of Xen event-channel device
Date: Fri, 28 May 2010 16:20:03 -0700	[thread overview]
Message-ID: <4C004FA3.1040004@goop.org> (raw)
In-Reply-To: <20100527171313.GB11358@wavehammer.waldi.eu.org>

On 05/27/2010 10:13 AM, Bastian Blank wrote:
> The udev rules will just not longer match, as they only rename the
> device, this is no problem. However libxc _will_ break, as it lacks
> proper error check in its own device creation routine.
>   

Yeah, that's really annoying.  I can't change the kernel without also
having a flag day to update libxc.  I guess we could make sure all the
stable Xen branches get a libxc fix backported to them, but I wonder if
it would break other toolstacks?

> However there are not much possibilities here: this support will go away
> and it will annoy every user for some time.
>   

But if we don't make any kernel changes then libxc will muddle on even
if udev stops handling the device name properly?

    J

  parent reply	other threads:[~2010-05-28 23:20 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       ` [Xen-devel] " Konrad Rzeszutek Wilk
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 [this message]
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=4C004FA3.1040004@goop.org \
    --to=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --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 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.