linux-kernel - Re: [PATCH 2/3] Better interface for hooking early initcalls.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 23 Jun 2008 00:05:16 +0300
From:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
To:	"Pekka Enberg" <penberg@...helsinki.fi>
Cc:	"Vegard Nossum" <vegard.nossum@...il.com>, tzanussi@...il.com,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	compudj@...stal.dyndns.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] Better interface for hooking early initcalls.

On Sun, 22 Jun 2008 23:45:57 +0300
"Pekka Enberg" <penberg@...helsinki.fi> wrote:

> On Sun, Jun 22, 2008 at 11:43 PM, Vegard Nossum
> <vegard.nossum@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/