From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Marc Marí" <markmb@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] Add dynamic module loading for block drivers
Date: Thu, 3 Sep 2015 17:33:16 +0100 [thread overview]
Message-ID: <20150903163316.GC18405@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1439798975-2488-2-git-send-email-markmb@redhat.com>
On Mon, Aug 17, 2015 at 10:09:34AM +0200, Marc Marí wrote:
> +static const struct {
> + const char *format_name;
> + const char *protocol_name;
> + const char *library_name;
> + bool has_probe;
> + bool has_probe_device;
> +} block_driver_module[] = {
Why is this list incomplete? It doesn't cover all block drivers.
Perhaps these are the only modular block drivers.
Also, it ignores CONFIG_CURL and friends. Perhaps it doesn't matter
because the module loading code will just see that there is no file
there, but maybe conditional compilation should be used?
A plural name would more consistent (i.e. you deleted the
plural block_modules[] variable and introduced a singular
block_driver_module[] variable).
next prev parent reply other threads:[~2015-09-03 16:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 8:09 [Qemu-devel] [PATCH 0/2] Dynamic module support for block drivers Marc Marí
2015-08-17 8:09 ` [Qemu-devel] [PATCH 1/2] Add dynamic module loading " Marc Marí
2015-08-27 9:19 ` Daniel P. Berrange
2015-08-27 9:35 ` Marc Marí
2015-08-27 9:40 ` Daniel P. Berrange
2015-09-03 16:33 ` Stefan Hajnoczi [this message]
2015-09-03 18:01 ` Marc Marí
2015-08-17 8:09 ` [Qemu-devel] [PATCH 2/2] Add dynamic generation of module_block.h Marc Marí
2015-08-27 9:23 ` Daniel P. Berrange
2015-08-27 9:37 ` Marc Marí
2015-08-27 8:51 ` [Qemu-devel] [PATCH 0/2] Dynamic module support for block drivers Marc Marí
2015-09-03 16:12 ` Stefan Hajnoczi
2015-09-03 18:07 ` Marc Marí
2015-09-07 13:09 ` 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=20150903163316.GC18405@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=markmb@redhat.com \
--cc=qemu-devel@nongnu.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).