public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: tip-bot for Peter Zijlstra <peterz@infradead.org>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
	a.p.zijlstra@chello.nl, peterz@infradead.org,
	isloginov@gmail.com, randy.dunlap@oracle.com, tglx@linutronix.de,
	mingo@elte.hu
Subject: [tip:sched/urgent] init: Fix comment
Date: Wed, 30 Jun 2010 08:45:46 GMT	[thread overview]
Message-ID: <tip-9715856922bf8475f5428c29b6f4a9eebc97d391@git.kernel.org> (raw)
In-Reply-To: <1277887031.1868.82.camel@laptop>

Commit-ID:  9715856922bf8475f5428c29b6f4a9eebc97d391
Gitweb:     http://git.kernel.org/tip/9715856922bf8475f5428c29b6f4a9eebc97d391
Author:     Peter Zijlstra <peterz@infradead.org>
AuthorDate: Wed, 30 Jun 2010 10:37:11 +0200
Committer:  Ingo Molnar <mingo@elte.hu>
CommitDate: Wed, 30 Jun 2010 10:42:44 +0200

init: Fix comment

Apparently "pid-1" confuses people...

Requested-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: torvalds@linux-foundation.org
Cc: randy.dunlap@oracle.com
Cc: Ilya Loginov <isloginov@gmail.com>
LKML-Reference: <1277887031.1868.82.camel@laptop>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 init/main.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/init/main.c b/init/main.c
index 633442f..1692df3 100644
--- a/init/main.c
+++ b/init/main.c
@@ -431,7 +431,7 @@ static noinline void __init_refok rest_init(void)
 
 	rcu_scheduler_starting();
 	/*
-	 * We need to spawn init first so that it obtains pid-1, however
+	 * We need to spawn init first so that it obtains pid 1, however
 	 * the init task will end up wanting to create kthreads, which, if
 	 * we schedule it before we create kthreadd, will OOPS.
 	 */

  reply	other threads:[~2010-06-30  8:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 20:11 [PATCH] fix problem with reschenduling in rest_init (2.6.35-rc3) Ilya Loginov
2010-06-24 13:11 ` Peter Zijlstra
2010-06-24 13:23   ` Ilya Loginov
2010-06-24 14:08     ` Илья Логинов
2010-06-28  9:01     ` [PATCH] init: Fix race between init and kthreadd Peter Zijlstra
2010-06-28 11:53       ` [PATCH] init: Fix race between init and kthreadd -v2 Peter Zijlstra
2010-06-28 14:19         ` Ingo Molnar
2010-06-28 14:51           ` [PATCH] init: Fix race between init and kthreadd -v3 Peter Zijlstra
2010-06-28 15:03             ` Linus Torvalds
2010-06-28 16:23             ` Randy Dunlap
2010-06-28 20:24             ` [tip:sched/urgent] init, sched: Fix race between init and kthreadd tip-bot for Peter Zijlstra
2010-06-30  8:32             ` [PATCH] init: Fix race between init and kthreadd -v3 Ilya Loginov
2010-06-30  8:37               ` [PATCH] init: Fix comment Peter Zijlstra
2010-06-30  8:45                 ` tip-bot for Peter Zijlstra [this message]
2010-06-28 20:06         ` [PATCH] init: Fix race between init and kthreadd -v2 Ilya Loginov

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=tip-9715856922bf8475f5428c29b6f4a9eebc97d391@git.kernel.org \
    --to=peterz@infradead.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=hpa@zytor.com \
    --cc=isloginov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=randy.dunlap@oracle.com \
    --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