From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] Splitting vl.h
Date: Sun, 11 Nov 2007 11:03:26 +0000 [thread overview]
Message-ID: <200711111103.28459.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580711110059l7901adc5u55cb3f4c86a78a13@mail.gmail.com>
On Sunday 11 November 2007, Blue Swirl wrote:
> On 11/11/07, Paul Brook <paul@codesourcery.com> wrote:
> > The attached patch starts splitting vl.h up a bit.
>
> I understand Fabrice's concern about small files, but I think this is
> the right direction.
Ok, I'll try to keep them to a minimum. e.g. I can combine cdrom.h and
scsi-disk.h
> In ide.c and esp.c there are TARGET_ and target_ dependencies, how do
> you plan to handle those?
Currently I don't, they will still be build per-target.
Longer term this is something a generic bus architecture should handle.
Paul
prev parent reply other threads:[~2007-11-11 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 4:22 [Qemu-devel] Splitting vl.h Paul Brook
2007-11-11 8:59 ` Blue Swirl
2007-11-11 11:03 ` Paul Brook [this message]
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=200711111103.28459.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=blauwirbel@gmail.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).