public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: davej@redhat.com
Cc: linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org
Subject: [PATCH 0/3] cpufreq / linux-next build fixes
Date: Tue, 17 Nov 2009 15:11:15 -0700	[thread overview]
Message-ID: <20091117220729.25933.57884.stgit@bob.kio> (raw)

Hi Dave,

I tripped over a build error when building /without/ CONFIG_CPU_FREQ.

I found this by way of the mmotm tree which I think sucks in linux-next.
I haven't checked your cpufreq tree directly, so apologies if these are
already fixed...

I build tested my changes with both CONFIG_CPU_FREQ set and unset, and
looked at the sparse output too, and all seems to be well. I did not
run-time test these changes.

Thanks,
/ac

---

Alex Chiang (3):
      [CPUFREQ] make ACPI P-state cpufreq drivers depend on CONFIG_CPU_FREQ
      ACPI: do not define acpi_processor_get_bios_limit() in processor.h
      [CPUFREQ] make internal cpufreq_add_dev_* static


 arch/x86/kernel/cpu/cpufreq/Kconfig |    6 +++---
 drivers/cpufreq/cpufreq.c           |    6 +++---
 include/acpi/processor.h            |    5 -----
 3 files changed, 6 insertions(+), 11 deletions(-)


             reply	other threads:[~2009-11-17 22:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 22:11 Alex Chiang [this message]
2009-11-17 22:11 ` [PATCH 1/3] [CPUFREQ] make ACPI P-state cpufreq drivers depend on CONFIG_CPU_FREQ Alex Chiang
2009-11-18  0:08   ` Dave Jones
2009-11-18  4:17     ` Alex Chiang
2009-11-17 22:11 ` [PATCH 2/3] ACPI: do not define acpi_processor_get_bios_limit() in processor.h Alex Chiang
2009-11-18  0:09   ` Dave Jones
2009-11-19 11:31     ` [PATCH] ACPI: do not define acpi_processor_get_bios_limit() in processor.h (snd ver) Thomas Renninger
2009-11-19 18:08       ` Alex Chiang
2009-11-17 22:11 ` [PATCH 3/3] [CPUFREQ] make internal cpufreq_add_dev_* static Alex Chiang
2009-11-18  0:29   ` Dave Jones
2009-11-18  3:27     ` [PATCH v2] " Alex Chiang

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=20091117220729.25933.57884.stgit@bob.kio \
    --to=achiang@hp.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox