From: Yodel Eldar <yodel.eldar@yodel.dev>
To: "Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>,
Kyle Evans <kevans@freebsd.org>, Warner Losh <imp@bsdimp.com>,
kvm@vger.kernel.org, Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH 0/7] cpus: Constify some CPUState arguments
Date: Thu, 30 Oct 2025 06:42:41 -0500 [thread overview]
Message-ID: <f1a0f03f-54b8-4fa8-8e03-b00a617bd462@yodel.dev> (raw)
In-Reply-To: <CAAjaMXZSkxCgzdC6w-onUxVxU_ZW5fiBtW5-ioeKaXwD_7tJeQ@mail.gmail.com>
On 30/10/2025 01:59, Manos Pitsidianakis wrote:
> On Wed, Oct 29, 2025 at 7:59 PM Philippe Mathieu-Daudé
> <philmd@linaro.org> wrote:
>>
>> On 20/1/25 07:13, Philippe Mathieu-Daudé wrote:
>>> This is in preparation of making various CPUClass handlers
>>> take a const CPUState argument.
>>>
>>> Philippe Mathieu-Daudé (7):
>>> qemu/thread: Constify qemu_thread_get_affinity() 'thread' argument
>>> qemu/thread: Constify qemu_thread_is_self() argument
>>> cpus: Constify qemu_cpu_is_self() argument
>>> cpus: Constify cpu_get_address_space() 'cpu' argument
>>> cpus: Constify cpu_is_stopped() argument
>>> cpus: Constify cpu_work_list_empty() argument
>>> accels: Constify AccelOpsClass::cpu_thread_is_idle() argument
>>
>> ping?
>>
>
> Hi Philippe, I can't find this series in my mailbox and it's not on
> lore.kernel.org/patchew/lists.gnu.org either. Resend?
>
Hi,
Looks like it landed on the kvm mailing list via Cc but was left out of
qemu-devel, despite the seemingly correct To header:
https://lore.kernel.org/kvm/20250120061310.81368-1-philmd@linaro.org/
Regards,
Yodel
prev parent reply other threads:[~2025-10-30 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250120061310.81368-1-philmd@linaro.org>
2025-10-29 17:58 ` [PATCH 0/7] cpus: Constify some CPUState arguments Philippe Mathieu-Daudé
2025-10-30 6:59 ` Manos Pitsidianakis
2025-10-30 11:42 ` Yodel Eldar [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=f1a0f03f-54b8-4fa8-8e03-b00a617bd462@yodel.dev \
--to=yodel.eldar@yodel.dev \
--cc=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=kvm@vger.kernel.org \
--cc=laurent@vivier.eu \
--cc=manos.pitsidianakis@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).