From: Fam Zheng <famz@redhat.com>
To: Richard Henderson <rth@twiddle.net>
Cc: peter.maydell@linaro.org, mjt@tls.msk.ru, qemu-devel@nongnu.org,
alex@alex.org.uk, pbonzini@redhat.com, vilanova@ac.upc.edu
Subject: Re: [Qemu-devel] [PATCH v10 5/8] module: implement module loading
Date: Tue, 17 Sep 2013 08:47:01 +0800 [thread overview]
Message-ID: <20130917004701.GA3362@T430s.nay.redhat.com> (raw)
In-Reply-To: <52378350.1020202@twiddle.net>
On Mon, 09/16 15:16, Richard Henderson wrote:
> On 09/16/2013 02:28 AM, Fam Zheng wrote:
> > What's the disadvantage of this, and why are separate lists better?
>
> You're performing useless work, making the code more confusing in the process.
> How can it not be better to have separate lists?
>
>
Because it's about adding more code in Makefile to separate them and adding
more code here to define and use multiple lists. I am not sure it's much more
readable than this, but it's really non critical question, let me first try to
do it.
Thanks,
Fam
next prev parent reply other threads:[~2013-09-17 0:47 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 6:50 [Qemu-devel] [PATCH v10 0/8] Shared Library Module Support Fam Zheng
2013-09-16 6:50 ` [Qemu-devel] [PATCH v10 1/8] ui/Makefile.objs: delete unnecessary cocoa.o dependency Fam Zheng
2013-09-16 6:50 ` [Qemu-devel] [PATCH v10 2/8] make.rule: fix $(obj) to a real relative path Fam Zheng
2013-09-16 6:50 ` [Qemu-devel] [PATCH v10 3/8] rule.mak: allow per object cflags and libs Fam Zheng
2013-09-16 6:50 ` [Qemu-devel] [PATCH v10 4/8] build-sys: introduce common-obj-m and block-obj-m for DSO Fam Zheng
2013-09-16 6:50 ` [Qemu-devel] [PATCH v10 5/8] module: implement module loading Fam Zheng
2013-09-16 8:59 ` Daniel P. Berrange
2013-09-16 9:28 ` Fam Zheng
2013-09-16 22:16 ` Richard Henderson
2013-09-17 0:47 ` Fam Zheng [this message]
2013-09-16 9:44 ` Paolo Bonzini
2013-09-16 9:51 ` Fam Zheng
2013-09-16 10:09 ` Paolo Bonzini
2013-09-16 10:14 ` Daniel P. Berrange
2013-09-16 10:18 ` Paolo Bonzini
2013-09-16 10:21 ` Daniel P. Berrange
2013-09-16 10:30 ` Paolo Bonzini
2013-09-16 11:29 ` Fam Zheng
2013-09-16 11:33 ` Paolo Bonzini
2013-09-16 11:46 ` Fam Zheng
2013-09-16 22:31 ` Richard Henderson
2013-09-17 1:29 ` Fam Zheng
2013-09-17 5:40 ` Richard Henderson
2013-09-18 11:45 ` Paolo Bonzini
2013-09-18 14:44 ` Richard Henderson
2013-09-18 15:00 ` Paolo Bonzini
2013-09-17 8:50 ` Wenchao Xia
2013-09-16 10:57 ` Gerd Hoffmann
2013-09-16 11:00 ` Paolo Bonzini
2013-09-16 22:38 ` Richard Henderson
2013-09-16 10:24 ` Alex Bligh
2013-09-16 10:38 ` Paolo Bonzini
2013-09-16 11:00 ` Alex Bligh
2013-09-16 11:04 ` Daniel P. Berrange
2013-09-16 11:27 ` Alex Bligh
2013-09-16 11:08 ` Paolo Bonzini
2013-09-16 11:30 ` Alex Bligh
2013-09-17 8:26 ` Wenchao Xia
2013-09-16 10:43 ` Fam Zheng
2013-09-16 11:05 ` Daniel P. Berrange
2013-09-16 12:36 ` Gerd Hoffmann
2013-09-17 5:55 ` Fam Zheng
2013-09-17 6:33 ` Alex Bligh
2013-09-17 6:40 ` Fam Zheng
2013-09-16 6:50 ` [Qemu-devel] [PATCH v10 6/8] Makefile: install modules with "make install" Fam Zheng
2013-09-16 6:50 ` [Qemu-devel] [PATCH v10 7/8] .gitignore: ignore module related files (dll, so, mo) Fam Zheng
2013-09-16 6:50 ` [Qemu-devel] [PATCH v10 8/8] block: convert block drivers linked with libs to modules Fam Zheng
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=20130917004701.GA3362@T430s.nay.redhat.com \
--to=famz@redhat.com \
--cc=alex@alex.org.uk \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=vilanova@ac.upc.edu \
/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).