All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] Fix cpufreq_{conservative,ondemand} compilation
Date: Fri, 23 Jun 2006 12:12:30 +0200	[thread overview]
Message-ID: <20060623121230.63e1237a.khali@linux-fr.org> (raw)

Fix cpufreq_conservative and cpufreq_ondemand, which were using
{lock,unlock}_cpu_hotplug without including linux/cpu.h which defines
them.

Signed-off-by: Jean Delvare <khali@linux-fr.org>
---
 drivers/cpufreq/cpufreq_conservative.c |    1 +
 drivers/cpufreq/cpufreq_ondemand.c     |    1 +
 2 files changed, 2 insertions(+)

--- linux-2.6.17-git.orig/drivers/cpufreq/cpufreq_conservative.c	2006-06-23 10:24:17.000000000 +0200
+++ linux-2.6.17-git/drivers/cpufreq/cpufreq_conservative.c	2006-06-23 12:07:42.000000000 +0200
@@ -17,6 +17,7 @@
 #include <linux/init.h>
 #include <linux/interrupt.h>
 #include <linux/ctype.h>
+#include <linux/cpu.h>
 #include <linux/cpufreq.h>
 #include <linux/sysctl.h>
 #include <linux/types.h>
--- linux-2.6.17-git.orig/drivers/cpufreq/cpufreq_ondemand.c	2006-06-23 10:24:17.000000000 +0200
+++ linux-2.6.17-git/drivers/cpufreq/cpufreq_ondemand.c	2006-06-23 12:07:34.000000000 +0200
@@ -16,6 +16,7 @@
 #include <linux/init.h>
 #include <linux/interrupt.h>
 #include <linux/ctype.h>
+#include <linux/cpu.h>
 #include <linux/cpufreq.h>
 #include <linux/sysctl.h>
 #include <linux/types.h>


-- 
Jean Delvare

             reply	other threads:[~2006-06-23 10:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 10:12 Jean Delvare [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-23 17:20 [PATCH] Fix cpufreq_{conservative,ondemand} compilation Pallipadi, Venkatesh
2006-06-23 19:50 ` Jean Delvare
2006-06-23 20:24 ` Krzysztof Halasa

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=20060623121230.63e1237a.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@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 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.