From: Andries.Brouwer@cwi.nl
To: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: [PATCH] setup_per_cpu_areas in 2.5.8pre3
Date: Sun, 14 Apr 2002 21:15:29 GMT [thread overview]
Message-ID: <UTC200204142115.VAA627059.aeb@cwi.nl> (raw)
Now that I am writing anyway, one of the changes I needed
to compile 2.5.8pre3 is the following.
--- main.c~ Fri Apr 12 12:10:48 2002
+++ main.c Sun Apr 14 16:11:33 2002
@@ -270,7 +270,9 @@
#else
#define smp_init() do { } while (0)
#endif
-
+static inline void setup_per_cpu_areas(void)
+{
+}
#else
#ifdef __GENERIC_PER_CPU
There is a nest of #ifdef's there, and in some branches
setup_per_cpu_areas() is not defined.
Of course the real fix is to remove the #ifdef's,
maybe using a weak symbol instead, or some other construction
that defines an empty default that can be replaced by an actual
routine.
Andries
next reply other threads:[~2002-04-14 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-14 21:15 Andries.Brouwer [this message]
2002-04-16 12:48 ` [PATCH] setup_per_cpu_areas in 2.5.8pre3 Rusty Russell
2002-04-17 8:24 Andries.Brouwer
2002-04-17 15:11 ` Tom Rini
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=UTC200204142115.VAA627059.aeb@cwi.nl \
--to=andries.brouwer@cwi.nl \
--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;
as well as URLs for NNTP newsgroup(s).