From: "Cédric Le Goater" <clg@kaod.org>
To: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Andrew Jeffery" <andrew@aj.id.au>,
"Joel Stanley" <joel@jms.id.au>,
"Cédric Le Goater" <clg@kaod.org>
Subject: [PATCH for 7.1 0/2] aspeed: QOM fixes
Date: Wed, 27 Jul 2022 12:27:12 +0200 [thread overview]
Message-ID: <20220727102714.803041-1-clg@kaod.org> (raw)
Hello,
Compiling with CONFIG_QOM_CAST_DEBUG caught a QOM issue in the fby35
machine. The series also includes a trivial cleanup of unused code.
Thanks,
C.
Cédric Le Goater (2):
aspeed: Remove unused fields from AspeedMachineState
aspeed/fby35: Fix owner of the BMC RAM memory region
hw/arm/aspeed.c | 2 --
hw/arm/fby35.c | 14 +++++++++-----
2 files changed, 9 insertions(+), 7 deletions(-)
--
2.37.1
next reply other threads:[~2022-07-27 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 10:27 Cédric Le Goater [this message]
2022-07-27 10:27 ` [PATCH for 7.1 1/2] aspeed: Remove unused fields from AspeedMachineState Cédric Le Goater
2022-07-27 10:27 ` [PATCH for 7.1 2/2] aspeed/fby35: Fix owner of the BMC RAM memory region Cédric Le Goater
2022-07-27 18:11 ` Peter Delevoryas
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=20220727102714.803041-1-clg@kaod.org \
--to=clg@kaod.org \
--cc=andrew@aj.id.au \
--cc=joel@jms.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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).