All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: patches@linaro.org, qemu-devel@nongnu.org,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/7] ARM boards: don't prematurely explode QEMUMachineInitArgs
Date: Wed, 24 Oct 2012 10:21:50 +0100	[thread overview]
Message-ID: <CAFEAcA9QkXKdSwPwOCdqxOJkbRUx4PFtF-m_ODM5v84NxQKWBw@mail.gmail.com> (raw)
In-Reply-To: <87d3088dm8.fsf@blackfin.pond.sub.org>

On 24 October 2012 09:42, Markus Armbruster <armbru@redhat.com> wrote:
> Peter Maydell <peter.maydell@linaro.org> writes:
>
>> A lot of the ARM board models follow the pattern of having a
>> single common init function which is called with various
>> parameters from the QEMUMachine init function for several board
>> model variants. The change to QEMUMachineInitArgs in commit 5f072e
>> took the fairly mechanical approach of splitting the QEMUMachineInitArgs
>> fields out in each variant's init function to pass to an unchanged
>> common init function. This is a bit repetitive, so clean them up
>> to just pass the QEMUMachineInitArgs directly to the common
>> function instead.
>
> A quick grep finds similar cleanup opportunities in
>
> hw/exynos4_boards.c     exynos4_boards_init_common()
> hw/pc_piix.c            pc_init1()
> hw/sun4m.c              sun4m_hw_init()
> hw/sun4u.c              sun4uv_init()
> hw/xtensa_lx60.c        lx_init()
> hw/xtensa_sim.c         sim_init()

I deliberately stuck to the ARM boards on the basis that the
others were a little out of my jurisdiction. I missed the
exynos4 though.

-- PMM

  reply	other threads:[~2012-10-24  9:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 17:04 [Qemu-devel] [PATCH 0/7] ARM boards: don't prematurely explode QEMUMachineInitArgs Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 1/7] hw/vexpress.c: Don't " Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 2/7] hw/realview.c: " Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 3/7] hw/versatilepb: " Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 4/7] hw/spitz: " Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 5/7] hw/omap_sx1: " Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 6/7] hw/nseries: " Peter Maydell
2012-10-23 17:04 ` [Qemu-devel] [PATCH 7/7] hw/mainstone: " Peter Maydell
2012-10-24  8:42 ` [Qemu-devel] [PATCH 0/7] ARM boards: don't " Markus Armbruster
2012-10-24  9:21   ` Peter Maydell [this message]
2012-10-24 12:06     ` Markus Armbruster
2012-10-24 12:10   ` Eduardo Habkost

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=CAFEAcA9QkXKdSwPwOCdqxOJkbRUx4PFtF-m_ODM5v84NxQKWBw@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=patches@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.