xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH for-4.7] Revert "libxl: No emulated disk driver for xvdX disk"
Date: Mon, 13 Jun 2016 09:41:41 +0100	[thread overview]
Message-ID: <CAFLBxZa73sC6Ku2dQJL_6uHKpkBLvHaCJzFPje8c8RTFGKETFg@mail.gmail.com> (raw)
In-Reply-To: <20160609132300.GA3583@aepfle.de>

On Thu, Jun 9, 2016 at 2:23 PM, Olaf Hering <olaf@aepfle.de> wrote:
> On Wed, Jun 08, Konrad Rzeszutek Wilk wrote:
>
>> On Wed, Jun 08, 2016 at 06:17:55PM +0200, Olaf Hering wrote:
>> > On Wed, Jun 08, George Dunlap wrote:
>> >
>> > > CC'ing Olaf and Konrad for their information. :-)
>> >
>> > I'm fine with the revert.
>
> Another case is pvgrub2, which also uses the 'dev' property to name the
> disk internally "xen/$vdev". Not sure if any generated grub.cfg actually
> contains tne name. But now that its reverted everything should continue
> to work as it did in xen-4.6.

Ah, so pvgrub2 follows the xenolinux code, rather than the pvops code?
 That should definitely be changed ASAP.

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-06-13  8:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 15:31 [PATCH for-4.7] Revert "libxl: No emulated disk driver for xvdX disk" Wei Liu
2016-06-08 15:32 ` Ian Jackson
2016-06-08 15:52   ` Wei Liu
2016-06-08 16:00     ` George Dunlap
2016-06-08 16:17       ` Olaf Hering
2016-06-08 17:55         ` Konrad Rzeszutek Wilk
2016-06-09 13:23           ` Olaf Hering
2016-06-13  8:41             ` George Dunlap [this message]
2016-06-13 10:21               ` Olaf Hering
2016-06-13 10:23                 ` George Dunlap

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=CAFLBxZa73sC6Ku2dQJL_6uHKpkBLvHaCJzFPje8c8RTFGKETFg@mail.gmail.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=olaf@aepfle.de \
    --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).