From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [RFC PATCH] timers: properly prefix init_clocks()
Date: Thu, 30 Oct 2025 23:13:10 +0100 [thread overview]
Message-ID: <ac02623e-df6a-4ed0-b973-08267c4e7d68@linaro.org> (raw)
In-Reply-To: <20251030173302.1379174-1-alex.bennee@linaro.org>
On 30/10/25 18:33, Alex Bennée wrote:
> Otherwise we run the risk of name clashing, for example with
> stm32l4x5_usart-test.c should we shuffle the includes.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> include/qemu/timer.h | 5 +++--
> tests/unit/test-aio-multithread.c | 2 +-
> util/main-loop.c | 2 +-
> util/qemu-timer.c | 2 +-
> 4 files changed, 6 insertions(+), 5 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2025-10-30 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 17:33 [RFC PATCH] timers: properly prefix init_clocks() Alex Bennée
2025-10-30 22:13 ` Philippe Mathieu-Daudé [this message]
2025-10-31 21:11 ` Philippe Mathieu-Daudé
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=ac02623e-df6a-4ed0-b973-08267c4e7d68@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--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).