From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel@lists.xen.org, m.a.young@durham.ac.uk
Subject: Re: [PATCH 1/2] tools/hotplug: introduce XENSTORED_ARGS= in sysconfig file.
Date: Thu, 8 Jan 2015 08:51:51 +0100 [thread overview]
Message-ID: <20150108075151.GB21024@aepfle.de> (raw)
In-Reply-To: <1420650712.18631.130.camel@citrix.com>
On Wed, Jan 07, Ian Campbell wrote:
> On Wed, 2015-01-07 at 16:49 +0000, Ian Jackson wrote:
> > Certainly removing this feature this late in the 4.5 release cycle is
> > not appropriate.
>
> I agree that faffing around with the initscripts/systemd units at the
> eleventh hour seem liable to leave us with a release where xenstored
> doesn't start or something.
What about staging, is that how it is supposed to look like in 4.6?
Or should I rather work on the wrapper script so that XENSTORED_TRACE
has to be used?
I would like to see patch #1 in 4.5 as the proper way to pass additional
options to xenstored.
Olaf
next prev parent reply other threads:[~2015-01-08 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 16:37 [PATCH 0/2] tools/hotplug/Linux changes Olaf Hering
2015-01-07 16:37 ` [PATCH 1/2] tools/hotplug: introduce XENSTORED_ARGS= in sysconfig file Olaf Hering
2015-01-07 16:44 ` Ian Campbell
2015-01-07 16:49 ` Ian Jackson
2015-01-07 17:11 ` Ian Campbell
2015-01-08 7:51 ` Olaf Hering [this message]
2015-01-08 19:09 ` Konrad Rzeszutek Wilk
2015-01-07 16:37 ` [PATCH 2/2] tools/hotplug: remove usage of XENSTORED_TRACE boolean Olaf Hering
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=20150108075151.GB21024@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=m.a.young@durham.ac.uk \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--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.