From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Splitting vl.h
Date: Sun, 11 Nov 2007 10:59:20 +0200 [thread overview]
Message-ID: <f43fc5580711110059l7901adc5u55cb3f4c86a78a13@mail.gmail.com> (raw)
In-Reply-To: <200711110422.24440.paul@codesourcery.com>
On 11/11/07, Paul Brook <paul@codesourcery.com> wrote:
> The attached patch starts splitting vl.h up a bit.
> I've pulled out the i2c, disk and irq code.
>
> Because I picked some of the easier ones, they can also be built once, rather
> than for every target.
>
> Obviously there's a lot left to do, but my grand plan is to get rid of vl.h
> altogether. A few files will probably end up effectively including
> everything, but hopefully most files should disentangle reasonably well. The
> more gets split out, the better things should get. e.g. scsi-disk.c doesn't
> need vl.h because I already split out the block API.
>
> I want to check this seems a reasonable approach before I go too much further.
> Comments?
I understand Fabrice's concern about small files, but I think this is
the right direction.
In ide.c and esp.c there are TARGET_ and target_ dependencies, how do
you plan to handle those?
next prev parent reply other threads:[~2007-11-11 8:59 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 [this message]
2007-11-11 11:03 ` Paul Brook
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=f43fc5580711110059l7901adc5u55cb3f4c86a78a13@mail.gmail.com \
--to=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).