qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Colin Lord <clord@redhat.com>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, den@openvz.org, qemu-devel@nongnu.org,
	qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] Dynamic module loading for block drivers
Date: Tue, 21 Jun 2016 18:59:58 +0200	[thread overview]
Message-ID: <54119adb-1ae2-b2a5-d1e4-32e967cc87a1@redhat.com> (raw)
In-Reply-To: <42716482-40e8-64f3-8f57-f6bde71f4c20@redhat.com>



On 21/06/2016 17:42, Colin Lord wrote:
> It could easily return the BlockDriver then
> using the name field. It seems to me that this would work, and would be
> a fairly minor change from how things are now (in particular I think
> that symlinks wouldn't be necessary with this).

Yes, I agree.

paolo

  reply	other threads:[~2016-06-21 17:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 18:40 [Qemu-devel] [PATCH 0/2] Dynamic module loading for block drivers Colin Lord
2016-06-15 18:40 ` [Qemu-devel] [PATCH 1/2] blockdev: Add dynamic generation of module_block.h Colin Lord
2016-06-15 22:48   ` Paolo Bonzini
2016-06-16  4:59   ` Fam Zheng
2016-06-16 13:57     ` Colin Lord
2016-06-17  9:57       ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2016-06-15 18:40 ` [Qemu-devel] [PATCH 2/2] blockdev: Add dynamic module loading for block drivers Colin Lord
2016-06-15 22:50   ` Paolo Bonzini
2016-06-16 14:00     ` Colin Lord
2016-06-16 14:05       ` Paolo Bonzini
2016-06-16 14:10         ` Colin Lord
2016-06-16 14:12           ` Paolo Bonzini
2016-06-17  9:54 ` [Qemu-devel] [Qemu-block] [PATCH 0/2] Dynamic " Stefan Hajnoczi
2016-06-20 15:32   ` Colin Lord
2016-06-21  9:32     ` Stefan Hajnoczi
2016-06-21 10:01       ` [Qemu-devel] " Paolo Bonzini
2016-06-21 15:42       ` [Qemu-devel] [Qemu-block] " Colin Lord
2016-06-21 16:59         ` Paolo Bonzini [this message]
2016-06-22 10:09           ` [Qemu-devel] " Stefan Hajnoczi

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=54119adb-1ae2-b2a5-d1e4-32e967cc87a1@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=clord@redhat.com \
    --cc=den@openvz.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).