From: Thomas Hood <jdthood@mail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: init_idle reaped before final call
Date: 05 Mar 2002 17:06:43 -0500 [thread overview]
Message-ID: <1015366005.1157.776.camel@thanatos> (raw)
I think you're right. To prevent the mistake from
happening again, I'd suggest you add a comment to your
patch for init_idle(), explaining that it can't be __init
because it is called by cpu_idle, which is called
by rest_init(), which ...
I wonder if an automated __init consistency checker
would be helpful.
--
Thomas Hood
next reply other threads:[~2002-03-05 22:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 22:06 Thomas Hood [this message]
2002-03-06 3:57 ` init_idle reaped before final call Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2002-03-05 19:58 Kip Walker
2002-03-05 19:56 Kip Walker
2002-03-05 21:57 ` Martin J. Bligh
2002-03-05 22:15 ` Kip Walker
2002-03-05 23:33 ` Justin Carlson
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=1015366005.1157.776.camel@thanatos \
--to=jdthood@mail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.