From: "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
To: "Cédric Le Goater" <clg@kaod.org>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
qemu-devel@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>,
Kane Chen <kane_chen@aspeedtech.com>,
Joel Stanley <joel@jms.id.au>,
qemu-arm@nongnu.org
Subject: Re: [PATCH] hw/misc/aspeed_scu: Set both AST2600 protection key registers on reset
Date: Wed, 19 Aug 2026 11:43:06 +0200 [thread overview]
Message-ID: <0d8ef450-d577-4bca-ac13-3994f4742852@oss.qualcomm.com> (raw)
In-Reply-To: <0be07514-48df-4168-8acf-8b082b3bebf5@kaod.org>
On 2026-08-19 9:17, Cédric Le Goater wrote:
> On 8/19/26 02:06, Philippe Mathieu-Daudé wrote:
>> On 18/8/26 03:43, Andrew Jeffery wrote:
>>> Currently, booting Linux on the ast2600-evb machine via -kernel results
>>> in a lot of warnings about failing to apply pinmux configuration when
>>> binding drivers:
[...]
>>> Fixes: e09cf36321f6 ("hw: aspeed_scu: Add AST2600 support")
>>> Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>
>>> ---
>>> I ran into this issue while improving test coverage in my patch review
>>> process.
>>> ---
>>> hw/misc/aspeed_scu.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> Cc: qemu-stable@nongnu.org
>> Fixes: e09cf36321f ("hw: aspeed_scu: Add AST2600 support")
>
> something is wrong with the above hash ?
Nop I just missed it.
>
> Thanks,
>
> C.
>
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@oss.qualcomm.com>
>
prev parent reply other threads:[~2026-08-19 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 1:43 [PATCH] hw/misc/aspeed_scu: Set both AST2600 protection key registers on reset Andrew Jeffery
2026-08-18 6:05 ` Jamin Lin
2026-08-18 21:20 ` Cédric Le Goater
2026-08-19 0:02 ` Andrew Jeffery
2026-08-19 0:06 ` Philippe Mathieu-Daudé
2026-08-19 7:17 ` Cédric Le Goater
2026-08-19 9:43 ` Philippe Mathieu-Daudé [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=0d8ef450-d577-4bca-ac13-3994f4742852@oss.qualcomm.com \
--to=philmd@oss.qualcomm.com \
--cc=andrew@codeconstruct.com.au \
--cc=clg@kaod.org \
--cc=jamin_lin@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=kane_chen@aspeedtech.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.