All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] add a way to disable xen's udev script.
Date: Thu, 9 Jun 2011 11:07:12 +0100	[thread overview]
Message-ID: <4DF09B50.1020401@eu.citrix.com> (raw)
In-Reply-To: <1307611406.775.781.camel@zakaz.uk.xensource.com>

On 06/09/2011 10:23 AM, Ian Campbell wrote:
> Feel free to suggest patches which implement any better scheme you have.
>    

I did already.

My solution involves going to step 2 directly, keeping a simple way for 
compat toolstacks to still work dynamically in parallel with new more 
modern toolstack that doesn't use those udev script. And eventually 
reach step 3 that will remove the udev scripts altogether (which render 
fancy tweaks in those udev scripts (step 1) absolutely moot)

Unfortunately you really want to go to step 1, before step 2 which 
involves doing lots of unnecessary work. I don't have any interest in 
that as stated above.

-- 
Vincent

  reply	other threads:[~2011-06-09 10:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 16:55 [PATCH] add a way to disable xen's udev script Vincent Hanquez
2011-06-08 17:42 ` Ian Campbell
2011-06-08 19:23   ` Vincent Hanquez
2011-06-08 19:49     ` Ian Campbell
2011-06-08 20:33       ` Vincent Hanquez
2011-06-09  7:42         ` Ian Campbell
2011-06-09  9:01           ` Vincent Hanquez
2011-06-09  9:23             ` Ian Campbell
2011-06-09 10:07               ` Vincent Hanquez [this message]
2011-06-10  7:13                 ` Ian Campbell
2011-06-13  8:58                   ` Vincent Hanquez
2011-06-14 13:36                     ` Ian Campbell
2011-06-17  7:45                       ` Vincent Hanquez
2011-06-17 17:23                       ` Ian Jackson

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=4DF09B50.1020401@eu.citrix.com \
    --to=vincent.hanquez@eu.citrix.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --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.