From: Ingo Molnar <mingo@kernel.org>
To: hpa@zytor.com, peterz@infradead.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:smp/hotplug] cpu/hotplug: Document states better
Date: Sun, 13 Mar 2016 11:29:34 +0100 [thread overview]
Message-ID: <20160313102934.GA20452@gmail.com> (raw)
In-Reply-To: <tip-d10ef6f9380b8853c4b48eb104268fccfdc0b0c5@git.kernel.org>
* tip-bot for Thomas Gleixner <tipbot@zytor.com> wrote:
> cpu/hotplug: Document states better
> [CPUHP_BRINGUP_CPU] = {
> .name = "cpu:bringup",
> .startup = bringup_cpu,
> .teardown = NULL,
> .cant_stop = true,
> },
> + /*
> + * Handled on controll processor until the plugged processor manages
> + * this itself.
s/control
> + /* Entry state on starting. Interrupts enabled from here on. Transient
> + * state for synchronsization */
s/synchronization
-ENONSTANDARDCOMMENT
Thanks,
Ingo
parent reply other threads:[~2016-03-13 10:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tip-d10ef6f9380b8853c4b48eb104268fccfdc0b0c5@git.kernel.org>]
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=20160313102934.GA20452@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.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