From: trix@redhat.com
To: jejb@linux.ibm.com, martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Tom Rix <trix@redhat.com>
Subject: [PATCH] scsi: lpfc: add depends CPU_FREQ to SCSI_LPFC configury
Date: Thu, 23 Jul 2020 07:01:36 -0700 [thread overview]
Message-ID: <20200723140136.18367-1-trix@redhat.com> (raw)
From: Tom Rix <trix@redhat.com>
A compile error
drivers/scsi/lpfc/lpfc_sli.c:7329:26: error: implicit
declaration of function ‘get_cpu_idle_time’; did you
mean ‘set_cpu_active’? [-Werror=implicit-function-declaration]
idle_stat->prev_idle = get_cpu_idle_time(i, &wall, 1);
lpfc_init_idle_stat_hb depends on CPU_FREQ
So add depends CPU_FREQ to the configury.
Signed-off-by: Tom Rix <trix@redhat.com>
---
drivers/scsi/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
index 571473a58f98..004dcda07d49 100644
--- a/drivers/scsi/Kconfig
+++ b/drivers/scsi/Kconfig
@@ -1157,6 +1157,7 @@ config SCSI_LPFC
depends on SCSI_FC_ATTRS
depends on NVME_TARGET_FC || NVME_TARGET_FC=n
depends on NVME_FC || NVME_FC=n
+ depends on CPU_FREQ
select CRC_T10DIF
help
This lpfc driver supports the Emulex LightPulse
--
2.18.1
reply other threads:[~2020-07-23 14:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200723140136.18367-1-trix@redhat.com \
--to=trix@redhat.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).