From: Ian Campbell <Ian.Campbell@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH] README: remove requirement for udev
Date: Thu, 23 Oct 2014 12:31:55 +0100 [thread overview]
Message-ID: <1414063915.1140.1.camel@citrix.com> (raw)
In-Reply-To: <1413976516.19198.2.camel@citrix.com>
On Wed, 2014-10-22 at 12:15 +0100, Ian Campbell wrote:
> On Tue, 2014-10-21 at 15:30 +0200, Olaf Hering wrote:
> > There is no requirement for udev during package build. It may be
> > required at runtime even with libxl with run_hotplug_scripts=yes
> > in xl.conf.
> >
> > Signed-off-by: Olaf Hering <olaf@aepfle.de>
> Acked-by: Ian Campbell <ian.campbell@citrix.com>
There were some comments but none of them seemed to invalidate the basic
premise of this patch so I've applied. Any other cleanups can be done
separately.
prev parent reply other threads:[~2014-10-23 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 13:30 [PATCH] README: remove requirement for udev Olaf Hering
2014-10-21 14:41 ` Wei Liu
2014-10-21 14:52 ` Olaf Hering
2014-10-21 14:57 ` Andrew Cooper
2014-10-21 15:10 ` Wei Liu
2014-10-22 11:15 ` Ian Campbell
2014-10-23 11:31 ` Ian Campbell [this message]
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=1414063915.1140.1.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xen.org \
/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.