From: "Andreas Färber" <afaerber@suse.de>
To: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qom-next v2 1/3] xilinx_zynq: Use cpu_arm_init() to obtain ARMCPU
Date: Mon, 21 May 2012 10:43:52 +0200 [thread overview]
Message-ID: <4FBA0048.9050100@suse.de> (raw)
In-Reply-To: <CAEgOgz4wZsmDQ+gFFQTOiVY9S-xsM6hdpy0x2Au09CMm6koULg@mail.gmail.com>
Am 21.05.2012 03:02, schrieb Peter Crosthwaite:
> Cant see it affecting the change pattern to the zynq boot though, so
> theres no blocker.
>
> Acked-by: Peter A.G. Crosthwaite <peter.crosthwaite@petalogix.com>
>
> On Sat, May 19, 2012 at 2:01 AM, Andreas Färber <afaerber@suse.de> wrote:
>> Needed for arm_load_kernel().
>>
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>> ---
>> hw/xilinx_zynq.c | 8 ++++----
>> 1 files changed, 4 insertions(+), 4 deletions(-)
Thanks, applied to qom-next:
http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/qom-next
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-05-21 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 16:01 [Qemu-devel] [PATCH qom-next v2 0/3] ARM: QOM cpu_reset() followups Andreas Färber
2012-05-18 16:01 ` [Qemu-devel] [PATCH qom-next v2 1/3] xilinx_zynq: Use cpu_arm_init() to obtain ARMCPU Andreas Färber
2012-05-21 1:02 ` Peter Crosthwaite
2012-05-21 8:43 ` Andreas Färber [this message]
2012-05-18 16:01 ` [Qemu-devel] [PATCH qom-next v2 2/3] arm_boot: Pass ARMCPU to arm_load_kernel() Andreas Färber
2012-05-18 16:02 ` [Qemu-devel] [PATCH qom-next v2 3/3] arm_pic: Pass ARMCPU to arm_pic_init_cpu() Andreas Färber
2012-05-23 15:05 ` [Qemu-devel] [PATCH qom-next v2 0/3] ARM: QOM cpu_reset() followups Andreas Färber
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=4FBA0048.9050100@suse.de \
--to=afaerber@suse.de \
--cc=peter.crosthwaite@petalogix.com \
--cc=peter.maydell@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 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).