From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: "Pekka Enberg" <penberg@cs.helsinki.fi>
Cc: "Vegard Nossum" <vegard.nossum@gmail.com>,
tzanussi@gmail.com, akpm@linux-foundation.org,
torvalds@linux-foundation.org, compudj@krystal.dyndns.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] Better interface for hooking early initcalls.
Date: Mon, 23 Jun 2008 00:05:16 +0300 [thread overview]
Message-ID: <20080623000516.450348bc@linux360.ro> (raw)
In-Reply-To: <84144f020806221345h6a429a0csfef6e3d8d80bdd6d@mail.gmail.com>
On Sun, 22 Jun 2008 23:45:57 +0300
"Pekka Enberg" <penberg@cs.helsinki.fi> wrote:
> On Sun, Jun 22, 2008 at 11:43 PM, Vegard Nossum
> <vegard.nossum@gmail.com> wrote:
> > By the way -- may I ask why it is called early_initcall() and not
> > pre_smp_initcall()? I think it makes sense to encode the exact
> > purpose of the initcall into the name. "early" is not very
> > explicit. This is just my opinion :-) Thanks.
>
> Sounds good to me.
Which one? :-)
I mean I could change the name, just let me know which one is better.
One encodes the purpose, while the other is consistent with CPU hotplug
stuff. Not that we couldn't change CPU hotplug docs to mention this,
this is an idea too.
next prev parent reply other threads:[~2008-06-22 21:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 14:10 [PATCH 2/3] Better interface for hooking early initcalls Eduard - Gabriel Munteanu
2008-06-22 19:22 ` Pekka Enberg
2008-06-22 20:38 ` Eduard - Gabriel Munteanu
2008-06-22 20:43 ` Vegard Nossum
2008-06-22 20:45 ` Pekka Enberg
2008-06-22 21:05 ` Eduard - Gabriel Munteanu [this message]
2008-06-22 21:01 ` Eduard - Gabriel Munteanu
-- strict thread matches above, loose matches on Subject: below --
2008-06-15 15:05 Eduard - Gabriel Munteanu
2008-06-17 14:07 ` Mathieu Desnoyers
2008-06-17 14:26 ` Eduard - Gabriel Munteanu
2008-06-17 14:43 ` Vegard Nossum
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=20080623000516.450348bc@linux360.ro \
--to=eduard.munteanu@linux360.ro \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@linux-foundation.org \
--cc=tzanussi@gmail.com \
--cc=vegard.nossum@gmail.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