From: Ian Campbell <ian.campbell@citrix.com>
To: Jim Fehlig <jfehlig@suse.com>,
Benjamin Beier <benjamin@desaster-games.com>,
Ian.Jackson@eu.citrix.com
Cc: Dario Faggioli <dario.faggioli@citrix.com>,
xen-devel@lists.xensource.com
Subject: Re: [BUG][4.5.1]xl cpupool-create segfault (with config file parameter)
Date: Tue, 1 Sep 2015 12:18:43 +0100 [thread overview]
Message-ID: <1441106323.27618.43.camel@citrix.com> (raw)
In-Reply-To: <55DE3CF0.3060306@suse.com>
On Wed, 2015-08-26 at 16:25 -0600, Jim Fehlig wrote:
> Sorry for jumping in late, but I encountered this issue yesterday with
> 4.5.1. Commit 705c9e12 fixes it and should probably be backported to the
> 4.5 branch.
Adding Ian J (tools stable maintainer) to To:
>
> Regards,
> Jim
>
next prev parent reply other threads:[~2015-09-01 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 11:03 [BUG][4.5.1]xl cpupool-create segfault (with config file parameter) Benjamin Beier
2015-08-12 11:28 ` Ian Campbell
2015-08-13 9:01 ` Dario Faggioli
2015-08-13 11:13 ` Benjamin Beier
2015-08-13 11:29 ` Ian Campbell
2015-08-13 12:12 ` Benjamin Beier
2015-08-26 22:25 ` Jim Fehlig
2015-09-01 11:18 ` Ian Campbell [this message]
2015-09-01 11:29 ` 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=1441106323.27618.43.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=benjamin@desaster-games.com \
--cc=dario.faggioli@citrix.com \
--cc=jfehlig@suse.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 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).