From: Andrew Morton <akpm@linux-foundation.org>
To: Sangjung Woo <sangjung.woo@samsung.com>
Cc: Rob Landley <rob@landley.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH] Documentation / CPU hotplug: Fix the typo in example code
Date: Wed, 15 Jan 2014 15:33:28 -0800 [thread overview]
Message-ID: <20140115153328.49a61c6bcd5897fad89af35c@linux-foundation.org> (raw)
In-Reply-To: <1389762626-28982-1-git-send-email-sangjung.woo@samsung.com>
On Wed, 15 Jan 2014 14:10:26 +0900 Sangjung Woo <sangjung.woo@samsung.com> wrote:
> As the notifier_block name (i.e. foobar_cpu_notifer) is different from
> the parameter (i.e.foobar_cpu_notifier) of register function, that is
> definitely error and it also makes readers confused.
>
btw, that document doesn't mention hotcpu_notifier(), which is actually
the preferred means of registration. Because it causes all the hotplug
code to be elided when CONFIG_HOTPLUG_CPU=n, without using ifdefs.
prev parent reply other threads:[~2014-01-15 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 5:10 Sangjung Woo
2014-01-15 5:45 ` Srivatsa S. Bhat
2014-01-15 23:33 ` Andrew Morton [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=20140115153328.49a61c6bcd5897fad89af35c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=rob@landley.net \
--cc=sangjung.woo@samsung.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
all inboxes | Powered by JetHome®