From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: "Cédric Le Goater" <clg@redhat.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Steven Lee <steven_lee@aspeedtech.com>,
Troy Lee <leetroy@gmail.com>,
Jamin Lin <jamin_lin@aspeedtech.com>,
Joel Stanley <joel@jms.id.au>
Subject: Re: [PATCH] aspeed: Remove duplicate typename in AspeedSoCClass
Date: Wed, 19 Feb 2025 12:06:01 +1030 [thread overview]
Message-ID: <090dbd8f11acbd3c166c62e3b0b7acdd1d6cb347.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20250218073534.585066-1-clg@redhat.com>
On Tue, 2025-02-18 at 08:35 +0100, Cédric Le Goater wrote:
> The SoC type name is stored under AspeedSoCClass which is
> redundant. Use object_get_typename() instead where needed.
>
> Signed-off-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Andrew Jeffery <andrew@codeconstruct.com.au>
prev parent reply other threads:[~2025-02-19 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 7:35 [PATCH] aspeed: Remove duplicate typename in AspeedSoCClass Cédric Le Goater
2025-02-19 1:36 ` Andrew Jeffery [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=090dbd8f11acbd3c166c62e3b0b7acdd1d6cb347.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=clg@redhat.com \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=leetroy@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=steven_lee@aspeedtech.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).