From: Rusty Russell <rusty@rustcorp.com.au>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] UP compilation fix for bk tree
Date: Tue, 30 Jul 2002 16:29:31 +1000 [thread overview]
Message-ID: <20020730093546.0C42244A5@lists.samba.org> (raw)
Simple, and when we resolve this initcall depends stuff, it will be
going away anyway.
Rusty.
--- working-2.5.29-upfix/init/main.c.~1~ Tue Jul 30 16:27:55 2002
+++ working-2.5.29-upfix/init/main.c Tue Jul 30 16:28:29 2002
@@ -529,7 +529,9 @@
extern int migration_init(void);
extern int spawn_ksoftirqd(void);
+#ifdef CONFIG_SMP
migration_init();
+#endif
spawn_ksoftirqd();
}
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
reply other threads:[~2002-07-30 9:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020730093546.0C42244A5@lists.samba.org \
--to=rusty@rustcorp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®