From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: Another bad usage of smp_processor_id
Date: Wed, 15 Sep 2010 01:14:34 +0200 [thread overview]
Message-ID: <1284506074.7596.0.camel@maxim-laptop> (raw)
In-Reply-To: <1284284277.2928.6.camel@maxim-laptop>
On Sun, 2010-09-12 at 11:37 +0200, Maxim Levitsky wrote:
> On Tue, 2010-09-07 at 11:18 +0300, Maxim Levitsky wrote:
> > On Fri, 2010-09-03 at 14:01 +0800, Zhang Rui wrote:
> > > Hi, Maxim,
> > >
> > > please try this patch and see if the problem still exists. :)
> > Yes it does :)
> > And its worse since my system now panics on resume...
> > Kernel log attached.
Ok. 2.6.36-rc4 fixes this.
Best regards,
Maxim Levitsky
prev parent reply other threads:[~2010-09-14 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 10:26 Another bad usage of smp_processor_id Maxim Levitsky
2010-09-01 10:25 ` Maxim Levitsky
2010-09-03 6:01 ` Zhang Rui
2010-09-07 8:18 ` Maxim Levitsky
2010-09-12 9:37 ` Maxim Levitsky
2010-09-14 23:14 ` Maxim Levitsky [this message]
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=1284506074.7596.0.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rui.zhang@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