From: Peter Maydell <peter.maydell@linaro.org>
To: Hongbo Zhang <hongbo.zhang@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
"Leif Lindholm" <leif.lindholm@linaro.org>,
"Radoslaw Biernacki" <radoslaw.biernacki@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v4] Add arm SBSA reference machine
Date: Mon, 5 Nov 2018 16:31:33 +0000 [thread overview]
Message-ID: <CAFEAcA8hB=+YKNc8WSxrdmqigtErOsPJSAhYnq0Ha8_Ey=NaMg@mail.gmail.com> (raw)
In-Reply-To: <1539939312-19713-1-git-send-email-hongbo.zhang@linaro.org>
On 19 October 2018 at 09:55, Hongbo Zhang <hongbo.zhang@linaro.org> wrote:
> For the Aarch64, there is one machine 'virt', it is primarily meant to
> run on KVM and execute virtualization workloads, but we need an
> environment as faithful as possible to physical hardware, to support
> firmware and OS development for pysical Aarch64 machines.
>
> See the patch commit comments for the features description.
>
> V4 changes:
> - rebased to v3.0.0
> - removed timer, uart, rtc, *hci device tree nodes
> (others were removerd in v3)
> - other minore codes clean up, mainly unsed header files, comments etc.
>
> V3 changes:
> - rename the platform 'sbsa-ref'
> - move all the codes to a separate file sbsa-ref.c
> - remove paravirtualized fw_cfg device
> - do not supply ACPI tables, since firmware will do it
> - supply only necessary DT nodes
> - and other minor code clean up
Hi; just a note that this series isn't going to make it into
the 3.1 release. It is still on my to-review queue for 4.0,
but I may not get to reviewing it for a little bit while I
deal with for-3.1 work.
thanks
-- PMM
next prev parent reply other threads:[~2018-11-05 16:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 8:55 [Qemu-devel] [PATCH v4] Add arm SBSA reference machine Hongbo Zhang
2018-10-19 8:55 ` [Qemu-devel] [PATCH v4] hw/arm: " Hongbo Zhang
2018-11-15 16:05 ` Peter Maydell
2018-11-16 10:46 ` Hongbo Zhang
2018-11-16 11:29 ` Peter Maydell
2018-11-19 10:49 ` Hongbo Zhang
2018-11-19 10:54 ` Hongbo Zhang
2018-12-06 9:19 ` Hongbo Zhang
2018-11-16 12:27 ` Gerd Hoffmann
2018-11-16 22:04 ` Ard Biesheuvel
2018-11-19 12:44 ` Leif Lindholm
2018-11-19 15:51 ` Ard Biesheuvel
2018-11-19 16:44 ` Leif Lindholm
2018-11-19 17:17 ` Ard Biesheuvel
2018-11-20 8:16 ` Gerd Hoffmann
2018-11-20 8:49 ` Hongbo Zhang
2018-11-20 9:40 ` Ard Biesheuvel
2018-11-21 8:35 ` Hongbo Zhang
2018-12-29 9:52 ` Hongbo Zhang
2018-11-23 7:14 ` Hongbo Zhang
2018-11-23 7:32 ` Hongbo Zhang
2018-12-05 9:50 ` Hongbo Zhang
2018-12-05 10:36 ` Leif Lindholm
2018-12-06 1:50 ` Hongbo Zhang
2019-01-29 11:28 ` Ard Biesheuvel
2019-01-30 8:34 ` Hongbo Zhang
2019-01-30 8:37 ` Ard Biesheuvel
2019-01-31 13:21 ` Radoslaw Biernacki
2018-11-05 16:31 ` Peter Maydell [this message]
2018-11-06 10:16 ` [Qemu-devel] [PATCH v4] " Hongbo Zhang
2018-11-15 16:20 ` Peter Maydell
2018-11-15 18:59 ` Ard Biesheuvel
2018-11-16 8:23 ` Hongbo Zhang
2018-11-16 9:58 ` Peter Maydell
2018-11-16 10:52 ` Hongbo Zhang
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='CAFEAcA8hB=+YKNc8WSxrdmqigtErOsPJSAhYnq0Ha8_Ey=NaMg@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=hongbo.zhang@linaro.org \
--cc=leif.lindholm@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=radoslaw.biernacki@linaro.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).