linux-kernel - Re: [PATCH 2/3] Full conversion to early_initcall() interface, remove old interface.

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 27 Jun 2008 11:45:15 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>
Cc:	hannes@...urebad.de, tzanussi@...il.com, penberg@...helsinki.fi,
	torvalds@...ux-foundation.org, compudj@...stal.dyndns.org,
	vegard.nossum@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] Full conversion to early_initcall() interface,
 remove old interface.

On Fri, 27 Jun 2008 14:28:00 +0300
Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro> wrote:

> On Fri, 27 Jun 2008 12:54:21 +0200
> Johannes Weiner <hannes@...urebad.de> wrote:
> 
> > Hi Eduard,
> 
> Hi.
>  
> > You forgot to remove the declaration from linux/interrupt.h.
> 
> The last patch was made against linux-next, as Andrew Morton
> suggested, where spawn_ksoftirqd() was declared in the scope of
> __do_pre_smp_initcall():
> @@ -793,17 +784,6 @@ static void __init __do_pre_smp_initcalls(void)
>  		do_one_initcall(*call);
>  }
>  
> -static void __init do_pre_smp_initcalls(void)
> -{
> -	extern int spawn_ksoftirqd(void);
> -
> -	init_call_single_data();
> -	migration_init();
> -	spawn_ksoftirqd();
> -	if (!nosoftlockup)
> -		spawn_softlockup_task();
> -}
> -
> 
> It may be that some other patch in -mmotm moves that into
> include/linux/interrupt.h. In linux-next with my patch, running
> $ find . -name \*.h | xargs grep "spawn_ksoftirqd"
> shows nothing.

Yes, I dropped that patch as it's no longer relevant.

> Thanks for spotting this difference.
> 
> (Using -mmotm + quilt myself is an additional headache, since git
> already does what I want in terms of patch (read commits) management;
> that's why I prefered linux-next.)

It is a bit of a pain.  I avoid asking people to raise patches against
-mm unless it's really necessary.
--
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/