public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: Johannes Weiner <hannes@saeurebad.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	tzanussi@gmail.com, penberg@cs.helsinki.fi,
	torvalds@linux-foundation.org, compudj@krystal.dyndns.org,
	vegard.nossum@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] Full conversion to early_initcall() interface, remove old interface.
Date: Fri, 27 Jun 2008 14:28:00 +0300	[thread overview]
Message-ID: <20080627142800.2c0b5cf1@linux360.ro> (raw)
In-Reply-To: <87d4m3ywpu.fsf@skyscraper.fehenstaub.lan>

On Fri, 27 Jun 2008 12:54:21 +0200
Johannes Weiner <hannes@saeurebad.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.

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.)

> Andrew, the following fix is needed for -mmotm:
> 
> From: Johannes Weiner <hannes@saeurebad.de>
> Subject:
> full-conversion-to-early_initcall-interface-remove-old-interface-fix
> 
> Original patch made spawn_softirqd() static but failed to remove the
> global definition.  Do so now.
> 
> Signed-off-by: Johannes Weiner <hannes@saeurebad.de>
> ---
> 
> diff --git a/include/linux/interrupt.h b/include/linux/interrupt.h
> index 30da779..62aa4f8 100644
> --- a/include/linux/interrupt.h
> +++ b/include/linux/interrupt.h
> @@ -299,7 +299,6 @@ extern void softirq_init(void);
>  #define __raise_softirq_irqoff(nr) do { or_softirq_pending(1UL <<
> (nr)); } while (0) extern void raise_softirq_irqoff(unsigned int nr);
>  extern void raise_softirq(unsigned int nr);
> -extern int spawn_ksoftirqd(void);
>  
>  
>  /* Tasklets --- multithreaded analogue of BHs.


	Cheers,
	Eduard

  reply	other threads:[~2008-06-27 11:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 12:30 [PATCH 2/3] Full conversion to early_initcall() interface, remove old interface Eduard - Gabriel Munteanu
2008-06-24  0:27 ` Andrew Morton
2008-06-25  9:01   ` Eduard - Gabriel Munteanu
2008-06-25  9:07     ` Eduard - Gabriel Munteanu
2008-06-27 10:54     ` Johannes Weiner
2008-06-27 11:28       ` Eduard - Gabriel Munteanu [this message]
2008-06-27 18:45         ` Andrew Morton
2008-06-27 19:41           ` Eduard - Gabriel Munteanu

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=20080627142800.2c0b5cf1@linux360.ro \
    --to=eduard.munteanu@linux360.ro \
    --cc=akpm@linux-foundation.org \
    --cc=compudj@krystal.dyndns.org \
    --cc=hannes@saeurebad.de \
    --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