From: Mike Travis <travis@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mingo@elte.hu, tglx@linutronix.de, ak@suse.de, clameter@sgi.com,
steiner@sgi.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, len.brown@intel.com,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2/4] acpi: change cpufreq tables to per_cpu variables
Date: Wed, 13 Feb 2008 10:10:00 -0800 [thread overview]
Message-ID: <47B33278.3060408@sgi.com> (raw)
In-Reply-To: <20080212153356.d2be3248.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Fri, 08 Feb 2008 15:37:40 -0800
> Mike Travis <travis@sgi.com> wrote:
>
>> Change cpufreq tables from arrays to per_cpu variables in
>> drivers/acpi/processor_thermal.c
>>
>> Based on linux-2.6.git + x86.git
>
> I fixed a bunch of rejects in "[PATCH 1/4] cpufreq: change cpu freq tables
> to per_cpu variables" and it compiles OK. But this one was beyond my
> should-i-repair-it threshold, sorry.
Should I rebase all the pending patches on 2.6.25-rc1 or 2.6.24-mm1
(or some other combination)?
Thanks,
Mike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-02-13 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 23:37 [PATCH 0/4] NR_CPUS: non-x86 arch specific reduction of NR_CPUS usage Mike Travis
2008-02-08 23:37 ` [PATCH 1/4] cpufreq: change cpu freq tables to per_cpu variables Mike Travis
2008-02-11 2:48 ` Dave Jones
2008-02-11 17:32 ` Mike Travis
2008-02-11 17:56 ` Dave Jones
2008-02-08 23:37 ` [PATCH 2/4] acpi: change cpufreq " Mike Travis
2008-02-12 23:33 ` Andrew Morton
2008-02-13 18:10 ` Mike Travis [this message]
2008-02-13 19:43 ` Andrew Morton
2008-02-08 23:37 ` [PATCH 3/4] oprofile: change cpu_buffer from array to per_cpu variable Mike Travis
2008-02-08 23:37 ` [PATCH 4/4] x86: minor cleanup of comments in processor.h Mike Travis
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=47B33278.3060408@sgi.com \
--to=travis@sgi.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).