public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: "Vegard Nossum" <vegard.nossum@gmail.com>
Cc: "Pekka Enberg" <penberg@cs.helsinki.fi>,
	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:01:02 +0300	[thread overview]
Message-ID: <20080623000102.2e364974@linux360.ro> (raw)
In-Reply-To: <19f34abd0806221343o3a9e3951j1448e968f9ba9684@mail.gmail.com>

On Sun, 22 Jun 2008 22:43:55 +0200
"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.

CPU hotplug docs name these (inexisting at that time) initcalls
'early', so I went on implementing 'early initcalls'. However, I don't
have strong feelings for either of these two names, so this could
change.

> Vegard
> 

  parent reply	other threads:[~2008-06-22 21:01 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
2008-06-22 21:01       ` Eduard - Gabriel Munteanu [this message]
  -- 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=20080623000102.2e364974@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