From: Dave Jones <davej@redhat.com>
To: Thomas Renninger <trenn@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhao Yakui <yakui.zhao@intel.com>, Len Brown <lenb@kernel.org>
Subject: Re: linux-next: manual merge of the cpufreq tree with the acpi tree
Date: Thu, 12 Nov 2009 12:13:56 -0500 [thread overview]
Message-ID: <20091112171356.GC2447@redhat.com> (raw)
In-Reply-To: <200911120615.38067.trenn@suse.de>
On Thu, Nov 12, 2009 at 06:15:37AM -0600, Thomas Renninger wrote:
> > evaluation status to the platform") from the acpi tree and commit
> > b02d803d0fa3a395ba32bc5e5e3e7a3385ca7237 ("[CPUFREQ] Introduce bios_limit
> > per cpu cpufreq sysfs interface") from the cpufreq tree.
> First, thanks everybody for picking this up.
np, apologies for the delay.
> > By the way, Dave, Thomas, shouldn't the second version of
> > acpi_processor_get_bios_limit() in include/acpi/processor.h introduced by
> > the above cpufreq tree patch be "static inline"?
> Yes, good catch.
> Shall I send an on top fix somewhere?
Yeah, an incremental will be fine. I'll fold it into the original.
thanks,
Dave
next prev parent reply other threads:[~2009-11-12 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 2:45 linux-next: manual merge of the cpufreq tree with the acpi tree Stephen Rothwell
2009-11-12 12:15 ` Thomas Renninger
2009-11-12 17:13 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-24 3:34 Stephen Rothwell
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=20091112171356.GC2447@redhat.com \
--to=davej@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=trenn@suse.de \
--cc=yakui.zhao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox