From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: fixing 2.6.10 UP builds
Date: Thu, 13 Jan 2005 00:20:43 +0000 [thread overview]
Message-ID: <200501121620.43791.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <20050106201427.GA6009@jale>
On Wednesday, January 12, 2005 4:02 pm, Luck, Tony wrote:
> >I've regenerated this patch, original developed by Jesse
> >Barnes, against 2.6.10, which fixes UP builds. I've also removed the
> > bogus header removals from the cyclone driver.
> >
> >I won't pretend to be able to explain the details, hopefully
> >Jesse recalls :)
>
> I think that I pulled together all the pieces, but I still see
> a couple of problems when trying to build a generic-UP kernel:
>
> CC drivers/char/mmtimer.o
> drivers/char/mmtimer.c: In function `mmtimer_tasklet':
> drivers/char/mmtimer.c:502: structure has no member named `write_lock'
> make[1]: *** [drivers/char/mmtimer.o] Error 1
> make: *** [drivers/char/mmtimer.o] Error 2
Looks like we need rwlock_is_write_locked for this one. Christoph?
> CC arch/ia64/sn/kernel/sn2/sn_hwperf.o
> In file included from arch/ia64/sn/kernel/sn2/sn_hwperf.c:33:
> include/linux/nodemask.h: In function `__first_unset_node':
> include/linux/nodemask.h:244: warning: passing arg 1 of
> `__find_next_zero_bit' discards qualifiers from pointer target type
This warning was introduced upstream with the nodemask stuff. It should be
fixed but is unrelated to the UP stuff.
> arch/ia64/sn/kernel/sn2/sn_hwperf.c: In function `sn_hwperf_op_cpu':
> arch/ia64/sn/kernel/sn2/sn_hwperf.c:360: warning: implicit declaration of
> function `smp_call_function_single'
Looks like we need a !CONFIG_SMP version of smp_call_function_single.
include/linux/smp.h has a non-smp version of smp_call_function that just
returns 0, should smp_call_function_single do the same thing?
Jesse
next prev parent reply other threads:[~2005-01-13 0:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 20:14 fixing 2.6.10 UP builds dann frazier
2005-01-06 21:31 ` Luck, Tony
2005-01-06 21:36 ` Christoph Hellwig
2005-01-06 21:54 ` Jesse Barnes
2005-01-06 21:59 ` Luck, Tony
2005-01-08 3:02 ` dann frazier
2005-01-13 0:02 ` Luck, Tony
2005-01-13 0:20 ` Jesse Barnes [this message]
2005-01-13 0:34 ` Luck, Tony
2005-01-13 0:36 ` Christoph Lameter
2005-01-13 0:50 ` Jesse Barnes
2005-01-13 0:55 ` Mark Goodwin
2005-01-13 1:42 ` Mark Goodwin
2005-01-13 8:14 ` Christoph Hellwig
2005-01-13 19:11 ` Christoph Lameter
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=200501121620.43791.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=linux-ia64@vger.kernel.org \
/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