From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: linux-next: Tree for Jan 5 (drivers/acpi/cppc_acpi.o)
Date: Wed, 5 Jan 2022 18:31:22 -0800 [thread overview]
Message-ID: <484af487-7511-647e-5c5b-33d4429acdec@infradead.org> (raw)
In-Reply-To: <20220105191239.26498b30@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 294 bytes --]
On 1/5/22 00:12, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20220104:
>
on x86_64:
ld: drivers/acpi/cppc_acpi.o: in function `acpi_cppc_processor_probe':
cppc_acpi.c:(.text+0xa38): undefined reference to `init_freq_invariance_cppc'
Full randconfig file is attached.
--
~Randy
[-- Attachment #2: config-r2008.gz --]
[-- Type: application/gzip, Size: 36252 bytes --]
prev parent reply other threads:[~2022-01-06 2:31 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
2022-01-06 2:31 ` Randy Dunlap [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=484af487-7511-647e-5c5b-33d4429acdec@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rafael@kernel.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 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).