From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Inès Varhol" <ines.varhol@telecom-paris.fr>, qemu-devel@nongnu.org
Cc: "Laurent Vivier" <lvivier@redhat.com>,
qemu-arm@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Damien Hedde" <damien.hedde@dahe.fr>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Luc Michel" <luc@lmichel.fr>,
"Arnaud Minier" <arnaud.minier@telecom-paris.fr>,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH v3 3/4] hw/clock: Expose 'qtest-clock-period' QOM property for QTests
Date: Tue, 28 May 2024 17:17:56 +0200 [thread overview]
Message-ID: <4d964d18-db2b-4282-b499-ca42ec8b6112@linaro.org> (raw)
In-Reply-To: <20240523194441.21036-4-ines.varhol@telecom-paris.fr>
On 23/5/24 21:41, Inès Varhol wrote:
> Expose the clock period via the QOM 'qtest-clock-period' property so it
> can be used in QTests. This property is only accessible in QTests (not
> via HMP).
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Addressing Luc and Peter comments, you can replace that line by:
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Thanks!
> Signed-off-by: Inès Varhol <ines.varhol@telecom-paris.fr>
> ---
> docs/devel/clocks.rst | 3 +++
> hw/core/clock.c | 16 ++++++++++++++++
> 2 files changed, 19 insertions(+)
next prev parent reply other threads:[~2024-05-28 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 19:41 [PATCH v3 0/4] Check clock connection between STM32L4x5 RCC and peripherals Inès Varhol
2024-05-23 19:41 ` [PATCH v3 1/4] hw/misc: Create STM32L4x5 SYSCFG clock Inès Varhol
2024-05-28 14:40 ` Peter Maydell
2024-05-29 6:27 ` Philippe Mathieu-Daudé
2024-05-23 19:41 ` [PATCH v3 2/4] hw/char: Use v2 VMStateDescription for STM32L4x5 USART Inès Varhol
2024-05-28 14:39 ` Peter Maydell
2024-05-23 19:41 ` [PATCH v3 3/4] hw/clock: Expose 'qtest-clock-period' QOM property for QTests Inès Varhol
2024-05-27 7:04 ` Luc Michel
2024-05-28 14:51 ` Peter Maydell
2024-05-28 15:17 ` Philippe Mathieu-Daudé [this message]
2024-05-23 19:41 ` [PATCH v3 4/4] tests/qtest: Check STM32L4x5 clock connections Inès Varhol
2024-05-28 14:49 ` 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=4d964d18-db2b-4282-b499-ca42ec8b6112@linaro.org \
--to=philmd@linaro.org \
--cc=arnaud.minier@telecom-paris.fr \
--cc=damien.hedde@dahe.fr \
--cc=ines.varhol@telecom-paris.fr \
--cc=luc@lmichel.fr \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).