From: Alex Chiang <achiang@hp.com>
To: Thomas Renninger <trenn@suse.de>
Cc: Dave Jones <davej@redhat.com>, Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org, cpufreq@vger.kernel.org
Subject: Re: [PATCH] ACPI: do not define acpi_processor_get_bios_limit() in processor.h (snd ver)
Date: Thu, 19 Nov 2009 11:08:05 -0700 [thread overview]
Message-ID: <20091119180805.GA4386@ldl.fc.hp.com> (raw)
In-Reply-To: <200911191231.02905.trenn@suse.de>
* Thomas Renninger <trenn@suse.de>:
> >
> > There's 2-3 other fixes pending for the bios_limit patch.
> Alex removed the function that should have get
> static inline and that looks like the right fix for two
> mentioned problems.
>
> > For now, I've dropped it from cpufreq.next, until Thomas sends
> > a rediffed version with the compilation problems fixed.
> Attached is my old version, merged with Alex's one.
> Alex drops out as author of the fix by that, hope that's ok
> with you.
That's fine, maybe do what akpm does...
[achiang@hp.com fix build breakage]
> CC: Pallipadi Venkatesh <venkatesh.pallipadi@intel.com>
> CC: Len Brown <lenb@kernel.org>
> CC: davej@codemonkey.org.uk
> CC: linux@dominikbrodowski.net
>
> Signed-off-by: Thomas Renninger <trenn@suse.de>
But either way is fine by me.
/ac
next prev parent reply other threads:[~2009-11-19 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 22:11 [PATCH 0/3] cpufreq / linux-next build fixes Alex Chiang
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 [this message]
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=20091119180805.GA4386@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
/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