From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@zip.com.au>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Linux v2.5.29
Date: Sat, 27 Jul 2002 17:12:47 +1000 [thread overview]
Message-ID: <20020727075743.37594417F@lists.samba.org> (raw)
In-Reply-To: Your message of "Fri, 26 Jul 2002 23:52:44 MST." <3D42433C.C3BB8F4D@zip.com.au>
In message <3D42433C.C3BB8F4D@zip.com.au> you write:
> While you're there, this register_cpu_notifier() call
> generates a compile warning on UP:
>
> softirq.c: In function `spawn_ksoftirqd':
> softirq.c:416: warning: statement with no effect
Thanks Andrew...
Name: Hot-plug CPU notifier warning fix
Author: Rusty Russell
Status: Trivial
D: As pointed out by Andrew Morton, this fixes:
D: softirq.c: In function `spawn_ksoftirqd':
D: softirq.c:416: warning: statement with no effect
This patch alters the boot sequence to "plug in" each CPU, one at a
diff -urpN -I \$.*\$ --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal linux-2.5.29/include/linux/smp.h working-2.5.29-register-cpu-fix/include/linux/smp.h
--- linux-2.5.29/include/linux/smp.h Sat Jul 27 15:24:39 2002
+++ working-2.5.29-register-cpu-fix/include/linux/smp.h Sat Jul 27 17:10:04 2002
@@ -101,9 +101,13 @@ static inline void smp_send_reschedule_a
#define this_cpu(var) var
/* Need to know about CPUs going up/down? */
-#define register_cpu_notifier(nb) 0
-#define unregister_cpu_notifier(nb) do { } while(0)
-
+static inline int register_cpu_notifier(struct notifier_block *nb)
+{
+ return 0;
+}
+static inline void unregister_cpu_notifier(struct notifier_block *nb)
+{
+}
#endif /* !SMP */
#define get_cpu() ({ preempt_disable(); smp_processor_id(); })
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next parent reply other threads:[~2002-07-27 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D42433C.C3BB8F4D@zip.com.au>
2002-07-27 7:12 ` Rusty Russell [this message]
2002-07-27 3:12 Linux v2.5.29 Linus Torvalds
2002-07-27 3:23 ` Linus Torvalds
2002-07-27 6:26 ` Rusty Russell
2002-07-27 11:40 ` Peter Osterlund
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=20020727075743.37594417F@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.