xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org, wei.liu2@citrix.com,
	m.a.young@durham.ac.uk
Subject: Re: [PATCH v2 for-4.6] libxl: handle read-only drives with qemu-xen
Date: Mon, 21 Sep 2015 12:53:48 +0100	[thread overview]
Message-ID: <1442836428.10338.58.camel@citrix.com> (raw)
In-Reply-To: <22008.17873.704727.417727@mariner.uk.xensource.com>

On Tue, 2015-09-15 at 17:22 +0100, Ian Jackson wrote:
> Stefano Stabellini writes ("[PATCH v2 for-4.6] libxl: handle read-only
> drives with qemu-xen"):
> > The current libxl code doesn't deal with read-only drives at all.
> > 
> > Upstream QEMU and qemu-xen only support read-only cdrom drives: make
> > sure to specify "readonly=on" for cdrom drives and return error in case
> > the user requested a non-cdrom read-only drive.
> 
> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>

I applied to staging and staging-4.6 with this Ack and Wei's say so
elsewhere.

  reply	other threads:[~2015-09-21 11:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15  9:52 [PATCH v2 for-4.6] libxl: handle read-only drives with qemu-xen Stefano Stabellini
2015-09-15 16:22 ` Ian Jackson
2015-09-21 11:53   ` Ian Campbell [this message]
2015-09-15 17:53 ` M A Young
2015-09-16 13:54   ` Ian Jackson
2015-09-17 11:13     ` Ian Campbell
2015-09-17 11:27       ` M A Young
2015-09-17 11:35       ` Wei Liu
2015-09-17 11:49         ` Ian Campbell
2015-09-17 12:04           ` Wei Liu
2015-09-17 17:58       ` Ian Jackson
2015-09-18  8:47         ` Ian Campbell
2015-09-16 14:14   ` Wei Liu
2015-09-16 14:23     ` M A Young

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=1442836428.10338.58.camel@citrix.com \
    --to=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.xenproject.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 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).