From: Paul Mundt <lethal@linux-sh.org>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: mingo@elte.hu, akpm@linux-foundation.org,
simon.kagstrom@netinsight.net, David.Woodhouse@intel.com,
linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: [PATCH v3] printk: fix delayed messages from CPU hotplug events
Date: Fri, 4 Jun 2010 14:20:18 +0900 [thread overview]
Message-ID: <20100604052018.GA2565@linux-sh.org> (raw)
In-Reply-To: <ee1bf4f9c158983acad0a4548229586128afad67@localhost>
On Thu, Jun 03, 2010 at 10:11:25PM -0700, Kevin Cernekee wrote:
> [Changes from v2:
>
> Use hotcpu_notifier - fix will only apply to hotplug events, not
> initial SMP boot
>
With the hotcpu notifier it looks good to me.
Reviewed-by: Paul Mundt <lethal@linux-sh.org>
next prev parent reply other threads:[~2010-06-04 5:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 5:11 [PATCH v3] printk: fix delayed messages from CPU hotplug events Kevin Cernekee
2010-06-04 5:20 ` Paul Mundt [this message]
2010-06-04 5:58 ` Andrew Morton
2010-06-06 1:29 ` Ralf Baechle
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=20100604052018.GA2565@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=David.Woodhouse@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cernekee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mingo@elte.hu \
--cc=simon.kagstrom@netinsight.net \
/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