From: Huang Rui <ray.huang@amd.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 5 (cpufreq/amd-pstate)
Date: Thu, 6 Jan 2022 10:22:08 +0800 [thread overview]
Message-ID: <YdZSUHl2iD2bo4p0@amd.com> (raw)
In-Reply-To: <20e286d4-25d7-fb6e-31a1-4349c805aae3@infradead.org>
On Thu, Jan 06, 2022 at 10:19:14AM +0800, Randy Dunlap wrote:
>
>
> On 1/5/22 00:12, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20220104:
> >
> > The pm tree lost its build failure.
> >
>
> on i386 and x86_64:
> # CONFIG_ACPI is not set
>
> In file included from ../drivers/cpufreq/amd-pstate.c:40:0:
> ../include/acpi/processor.h:226:2: error: unknown type name ‘phys_cpuid_t’
> phys_cpuid_t phys_id; /* CPU hardware ID such as APIC ID for x86 */
> ^~~~~~~~~~~~
> ../include/acpi/processor.h:355:1: error: unknown type name ‘phys_cpuid_t’; did you mean ‘phys_addr_t’?
> phys_cpuid_t acpi_get_phys_id(acpi_handle, int type, u32 acpi_id);
> ^~~~~~~~~~~~
> phys_addr_t
> CC drivers/rtc/rtc-rv3029c2.o
> ../include/acpi/processor.h:356:1: error: unknown type name ‘phys_cpuid_t’; did you mean ‘phys_addr_t’?
> phys_cpuid_t acpi_map_madt_entry(u32 acpi_id);
> ^~~~~~~~~~~~
> phys_addr_t
> ../include/acpi/processor.h:357:20: error: unknown type name ‘phys_cpuid_t’; did you mean ‘phys_addr_t’?
> int acpi_map_cpuid(phys_cpuid_t phys_id, u32 acpi_id);
> ^~~~~~~~~~~~
> phys_addr_t
>
Thanks to report this, let me take a look.
Ray
next prev parent reply other threads:[~2022-01-06 2:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 8:12 linux-next: Tree for Jan 5 Stephen Rothwell
2022-01-06 2:19 ` linux-next: Tree for Jan 5 (cpufreq/amd-pstate) Randy Dunlap
2022-01-06 2:22 ` Huang Rui [this message]
2022-01-06 2:31 ` linux-next: Tree for Jan 5 (drivers/acpi/cppc_acpi.o) Randy Dunlap
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=YdZSUHl2iD2bo4p0@amd.com \
--to=ray.huang@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.