From: "Cédric Le Goater" <clg@kaod.org>
To: Joel Stanley <joel@jms.id.au>, Peter Maydell <peter.maydell@linaro.org>
Cc: Andrew Jeffery <andrew@aj.id.au>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] aspeed/scu: Implement chip id register
Date: Tue, 21 Jan 2020 08:23:29 +0100 [thread overview]
Message-ID: <d5c9af12-9970-1a6e-e88c-b8dc1901527b@kaod.org> (raw)
In-Reply-To: <20200121013302.43839-1-joel@jms.id.au>
On 1/21/20 2:33 AM, Joel Stanley wrote:
> This implements the chip id register in the SCU for the ast2500 and
> ast2600. The first patch is a cleanup to separate out ast2400 and
> ast2500 functionality.
These patches apply cleanly on top of :
[v3,0/5] aspeed: extensions and fixes
http://patchwork.ozlabs.org/cover/1222667/
Thanks,
C.
>
> Joel Stanley (2):
> aspeed/scu: Create separate write callbacks
> aspeed/scu: Implement chip ID register
>
> hw/misc/aspeed_scu.c | 93 +++++++++++++++++++++++++++++++++-----------
> 1 file changed, 70 insertions(+), 23 deletions(-)
>
next prev parent reply other threads:[~2020-01-21 7:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 1:33 [PATCH 0/2] aspeed/scu: Implement chip id register Joel Stanley
2020-01-21 1:33 ` [PATCH 1/2] aspeed/scu: Create separate write callbacks Joel Stanley
2020-01-21 4:20 ` Andrew Jeffery
2020-01-21 7:23 ` Cédric Le Goater
2020-01-21 8:50 ` Philippe Mathieu-Daudé
2020-01-21 1:33 ` [PATCH 2/2] aspeed/scu: Implement chip ID register Joel Stanley
2020-01-21 4:23 ` Andrew Jeffery
2020-01-21 7:23 ` Cédric Le Goater
2020-01-21 8:52 ` Philippe Mathieu-Daudé
2020-01-21 7:23 ` Cédric Le Goater [this message]
2020-02-17 9:29 ` [PATCH 0/2] aspeed/scu: Implement chip id register Cédric Le Goater
2020-02-17 10:24 ` Peter Maydell
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=d5c9af12-9970-1a6e-e88c-b8dc1901527b@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).