From: Jiri Slaby <jirislaby@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Brown, Len" <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
Yong Wang <yong.y.wang@linux.intel.com>
Subject: Re: resume crashes in intel_init_thermal [was: mmotm 2009-11-13-19-59 uploaded]
Date: Sat, 14 Nov 2009 19:44:36 +0100 [thread overview]
Message-ID: <4AFEFA94.8060207@gmail.com> (raw)
In-Reply-To: <20091114081549.1477fabc.akpm@linux-foundation.org>
On 11/14/2009 05:15 PM, Andrew Morton wrote:
> Revert
>
> : commit ce6b5d768c79b9d5dd6345c033bae781d5ca9b8e
> : Author: Yong Wang <yong.y.wang@linux.intel.com>
> : AuthorDate: Wed Nov 11 15:51:25 2009 +0800
> : Commit: Ingo Molnar <mingo@elte.hu>
> : CommitDate: Wed Nov 11 12:33:32 2009 +0100
> :
> : x86: Mark the thermal init functions __init
>
> because intel_init_thermal() is called from mce_intel_feature_init() at
> resume time, and we'd like its text to still be in memory when that
> happens.
Works for me. Thanks.
--
js
Faculty of Informatics, Masaryk University
Suse Labs, Novell
next prev parent reply other threads:[~2009-11-14 18:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 4:03 mmotm 2009-11-13-19-59 uploaded akpm
2009-11-14 13:28 ` resume crashes in intel_init_thermal [was: mmotm 2009-11-13-19-59 uploaded] Jiri Slaby
2009-11-14 13:28 ` Jiri Slaby
2009-11-14 16:15 ` Andrew Morton
2009-11-14 16:15 ` Andrew Morton
2009-11-14 18:44 ` Jiri Slaby
2009-11-14 18:44 ` Jiri Slaby [this message]
2009-11-15 8:07 ` Ingo Molnar
2009-11-15 8:07 ` Ingo Molnar
2009-11-16 21:09 ` mmotm 2009-11-13-19-59 uploaded Alex Chiang
2009-11-16 21:36 ` Andrew Morton
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=4AFEFA94.8060207@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=x86@kernel.org \
--cc=yong.y.wang@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.