From: Ingo Molnar <mingo@elte.hu>
To: Adrian Bunk <bunk@kernel.org>
Cc: Chris Clayton <chris2553@googlemail.com>,
tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] x86 intel_cacheinfo.c section fix
Date: Tue, 4 Dec 2007 13:56:07 +0100 [thread overview]
Message-ID: <20071204125607.GD31590@elte.hu> (raw)
In-Reply-To: <20071202004248.GF15974@stusta.de>
* Adrian Bunk <bunk@kernel.org> wrote:
> free_cache_attributes() must be __cpuinit since it calls the __cpuinit
> cache_remove_shared_cpu_map().
thanks, picked this up as a .24 fix.
Ingo
next prev parent reply other threads:[~2007-12-04 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 14:19 2.6.24-rc3-git4 build warnings Chris Clayton
2007-11-29 18:00 ` Adrian Bunk
2007-11-30 10:41 ` Chris Clayton
2007-12-01 19:36 ` Adrian Bunk
2007-12-01 19:49 ` Chris Clayton
2007-12-01 20:01 ` Adrian Bunk
2007-12-02 0:42 ` [2.6 patch] x86 intel_cacheinfo.c section fix Adrian Bunk
2007-12-04 12:56 ` Ingo Molnar [this message]
2007-12-02 0:43 ` [2.6 patch] drivers/cpufreq/cpufreq_stats.c " Adrian Bunk
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=20071204125607.GD31590@elte.hu \
--to=mingo@elte.hu \
--cc=bunk@kernel.org \
--cc=chris2553@googlemail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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).