From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Zhao Liu <zhao1.liu@intel.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Igor Mammedov <imammedo@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Ani Sinha <anisinha@redhat.com>,
Bernhard Beschow <shentey@gmail.com>,
Eduardo Habkost <eduardo@habkost.net>,
qemu-trivial@nongnu.org
Subject: Re: [PATCH 5/5] hw/i386/q35: Include missing 'hw/acpi/acpi.h' header
Date: Tue, 20 Feb 2024 08:10:43 +0100 [thread overview]
Message-ID: <7cae30fb-2a84-4a59-b7d9-d02c0807cede@linaro.org> (raw)
In-Reply-To: <ZdQSOiQiRxoEoR58@intel.com>
On 20/2/24 03:45, Zhao Liu wrote:
> Hi Philippe,
>
> On Mon, Feb 19, 2024 at 03:14:11PM +0100, Philippe Mathieu-Daudé wrote:
>> Date: Mon, 19 Feb 2024 15:14:11 +0100
>> From: Philippe Mathieu-Daudé <philmd@linaro.org>
>> Subject: [PATCH 5/5] hw/i386/q35: Include missing 'hw/acpi/acpi.h' header
>> X-Mailer: git-send-email 2.41.0
>>
>> "hw/acpi/acpi.h" is implicitly included.
>> Included it
>
> I'm guessing it's an imperative and shouldn't be in passive form. ;-) So,
>
> s/Included/Include/
>
>> explicitly to avoid when refactoring headers:
>
> s/to avoid/to avoid the following error/
Oops, thanks :)
>
>>
>> hw/i386/pc_q35.c:209:43: error: use of undeclared identifier 'ACPI_PM_PROP_ACPI_PCIHP_BRIDGE'
>> ACPI_PM_PROP_ACPI_PCIHP_BRIDGE,
>> ^
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> ---
>> hw/i386/pc_q35.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/hw/i386/pc_q35.c b/hw/i386/pc_q35.c
>> index d346fa3b1d..a91f414922 100644
>> --- a/hw/i386/pc_q35.c
>> +++ b/hw/i386/pc_q35.c
>> @@ -58,6 +58,7 @@
>> #include "hw/hyperv/vmbus-bridge.h"
>> #include "hw/mem/nvdimm.h"
>> #include "hw/i386/acpi-build.h"
>> +#include "hw/acpi/acpi.h"
>> #include "target/i386/cpu.h"
>
> Here it is unordered, and similarly, does it need to be sorted
> alphabetically here?
It shouldn't hurt ;)
prev parent reply other threads:[~2024-02-20 7:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 14:14 [PATCH 0/5] hw/acpi: Include missing headers Philippe Mathieu-Daudé
2024-02-19 14:14 ` [PATCH 1/5] hw/acpi: Include missing 'qapi/qapi-types-acpi.h' generated header Philippe Mathieu-Daudé
2024-02-20 2:29 ` Zhao Liu
2024-02-19 14:14 ` [PATCH 2/5] hw/acpi/cpu: Use CPUState typedef Philippe Mathieu-Daudé
2024-02-19 14:14 ` [PATCH 3/5] hw/acpi/ich9: Include missing headers Philippe Mathieu-Daudé
2024-02-20 2:33 ` Zhao Liu
2024-02-20 7:09 ` Philippe Mathieu-Daudé
2024-02-19 14:14 ` [PATCH 4/5] hw/acpi/ich9_tco: Include missing 'migration/vmstate.h' header Philippe Mathieu-Daudé
2024-02-20 2:35 ` Zhao Liu
2024-02-19 14:14 ` [PATCH 5/5] hw/i386/q35: Include missing 'hw/acpi/acpi.h' header Philippe Mathieu-Daudé
2024-02-20 2:45 ` Zhao Liu
2024-02-20 7:10 ` 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=7cae30fb-2a84-4a59-b7d9-d02c0807cede@linaro.org \
--to=philmd@linaro.org \
--cc=anisinha@redhat.com \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shentey@gmail.com \
--cc=zhao1.liu@intel.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).