From: Gustavo Romero <gustavo.romero@linaro.org>
To: eric.auger@redhat.com, qemu-devel@nongnu.org,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-trivial@nongnu.org, philmd@linaro.org
Subject: Re: [PATCH] hw/acpi/pcihp: Fix typo in function name
Date: Mon, 5 May 2025 21:26:35 -0300 [thread overview]
Message-ID: <5b507a45-133d-4340-b677-e8fc49bfbfd8@linaro.org> (raw)
In-Reply-To: <c66f47ae-ccb9-47b2-9bbe-fb1386958e6f@redhat.com>
Hi Eric,
On 5/5/25 11:19, Eric Auger wrote:
> Hi Gustavo,
>
> On 5/5/25 2:29 PM, Gustavo Romero wrote:
>> Hi Eric,
>>
>> On 5/5/25 04:13, Eric Auger wrote:
>>>
>>>
>>> On 5/4/25 11:56 PM, Gustavo Romero wrote:
>>>> Fix typo in QEMU's ACPI PCI hotplug API function name that checks
>>>> whether a given bus is hotplug-capable.
>>>>
>>>> Signed-off-by: Gustavo Romero <gustavo.romero@linaro.org>
>>> Reviewed-by: Eric Auger <eric.auger@redhat.com>
>>>
>>> For awareness, there is a similar typo in pci-port.
>>> see
>>> https://lore.kernel.org/all/20250428102628.378046-2-eric.auger@redhat.com/
>>>
>>
>> hmm it's unfortunate that I was about to publish a series to exactly
>> enable the APCI PCI hotplug on ARM. Next time I should try to sync better
>> with Red Hat folks on the work fronts...
> Sorry to hear that. That's always a frustrating situation :-(
Yes...
>> I've skimmed through your RFC and it seems to be doing mostly of what I
>> was doing for my series, so I'll reviewed it formally today, it should
>> be quick.
> I guess we may need to add some additional qtests for hotplug (just as
> they have on x86). Maybe we can collaborate on this or you already have
> some stuff under work.
Sure, the new test I'm baking is the one I've used in the smoke test. I'll
contribute it on top of your series so.
For the x86 "parity", which tests you're thinking of to add for arm64?
Cheers,
Gustavo
next prev parent reply other threads:[~2025-05-06 0:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-04 21:56 [PATCH] hw/acpi/pcihp: Fix typo in function name Gustavo Romero
2025-05-05 7:13 ` Eric Auger
2025-05-05 12:29 ` Gustavo Romero
2025-05-05 14:19 ` Eric Auger
2025-05-06 0:26 ` Gustavo Romero [this message]
2025-05-06 8:58 ` Eric Auger
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=5b507a45-133d-4340-b677-e8fc49bfbfd8@linaro.org \
--to=gustavo.romero@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=eric.auger@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).