From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Bernhard Beschow <shentey@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [PATCH 0/4] E500 cleanups and enhancements
Date: Sat, 28 Jan 2023 20:33:29 -0300 [thread overview]
Message-ID: <808dc3a5-eb7f-0331-99c1-d6cdbeb81cf7@gmail.com> (raw)
In-Reply-To: <20230125130024.158721-1-shentey@gmail.com>
On 1/25/23 10:00, Bernhard Beschow wrote:
> This series includes some cleanups I came across when working on the ppce500
> machine. Furthermore, it enables support for the 'dumpdtb' QMP/HMP command
> which was missing so far.
>
> Bernhard Beschow (4):
> hw/ppc: Set machine->fdt in e500 machines
> hw/ppc/e500{,plat}: Drop redundant checks for presence of platform bus
> hw/ppc/e500.c: Avoid hardcoding parent device in
> create_devtree_etsec()
> hw/ppc/e500.c: Attach eSDHC unimplemented region to ccsr_addr_space
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
And queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
>
> hw/ppc/e500.c | 24 ++++++++++++++++--------
> hw/ppc/e500plat.c | 9 +++------
> 2 files changed, 19 insertions(+), 14 deletions(-)
>
prev parent reply other threads:[~2023-01-28 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 13:00 [PATCH 0/4] E500 cleanups and enhancements Bernhard Beschow
2023-01-25 13:00 ` [PATCH 1/4] hw/ppc: Set machine->fdt in e500 machines Bernhard Beschow
2023-01-26 15:58 ` Daniel Henrique Barboza
2023-01-26 16:38 ` Bernhard Beschow
2023-01-25 13:00 ` [PATCH 2/4] hw/ppc/e500{, plat}: Drop redundant checks for presence of platform bus Bernhard Beschow
2023-01-25 13:00 ` [PATCH 3/4] hw/ppc/e500.c: Avoid hardcoding parent device in create_devtree_etsec() Bernhard Beschow
2023-01-25 13:00 ` [PATCH 4/4] hw/ppc/e500.c: Attach eSDHC unimplemented region to ccsr_addr_space Bernhard Beschow
2023-01-25 23:17 ` Philippe Mathieu-Daudé
2023-01-28 23:33 ` Daniel Henrique Barboza [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=808dc3a5-eb7f-0331-99c1-d6cdbeb81cf7@gmail.com \
--to=danielhb413@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=shentey@gmail.com \
/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).