From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Thara Gopinath <thara.gopinath@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: qcom-cpufreq-hw: Fix 'make allmodconfig' build
Date: Sun, 22 Aug 2021 17:14:04 -0400 [thread overview]
Message-ID: <440653.1629666844@turing-police> (raw)
In-Reply-To: <2bf9925a-fad9-ad9a-c878-daa08fae7e07@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
On Sun, 22 Aug 2021 14:08:08 -0700, Randy Dunlap said:
> This fixes one build error for me but I am still seeing another one:
>
> ERROR: modpost: "cpu_scale" [drivers/cpufreq/qcom-cpufreq-hw.ko] undefined!
That's a different patch, am working on fixing that one now..
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2021-08-22 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 20:10 [PATCH] cpufreq: qcom-cpufreq-hw: Fix 'make allmodconfig' build Valdis Klētnieks
2021-08-22 21:08 ` Randy Dunlap
2021-08-22 21:14 ` Valdis Klētnieks [this message]
2021-08-24 9:14 ` SeongJae Park
2021-08-25 2:16 ` Valdis Klētnieks
2021-08-25 4:41 ` SeongJae Park
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=440653.1629666844@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sudeep.holla@arm.com \
--cc=thara.gopinath@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 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.