From: Paul Larson <plars@linuxtestproject.org>
To: Andrew Morton <akpm@digeo.com>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: 2.5.70-mm4
Date: 04 Jun 2003 08:55:19 -0500 [thread overview]
Message-ID: <1054734923.8311.149.camel@plars> (raw)
In-Reply-To: <20030603231827.0e635332.akpm@digeo.com>
See bug 772 - http://bugme.osdl.org/show_bug.cgi?id=772
----------------------
CC kernel/ksyms.o
kernel/ksyms.c:490: `__preempt_spin_lock' undeclared here (not in a
function)
kernel/ksyms.c:490: initializer element is not constant
kernel/ksyms.c:490: (near initialization for
`__ksymtab___preempt_spin_lock.value')
kernel/ksyms.c:491: `__preempt_write_lock' undeclared here (not in a
function)
kernel/ksyms.c:491: initializer element is not constant
kernel/ksyms.c:491: (near initialization for
`__ksymtab___preempt_write_lock.value')
make[1]: *** [kernel/ksyms.o] Error 1
make: *** [kernel] Error 2
It looks like this got broken in /include/linux/spinlock.h:
#if defined(CONFIG_SMP) && defined(CONFIG_PREEMPT) &&
!defined(CONFIG_DEBUG_EVENTLOG)
void __preempt_spin_lock(spinlock_t *lock);
void __preempt_write_lock(rwlock_t *lock);
...
WARNING: multiple messages have this Message-ID (diff)
From: Paul Larson <plars@linuxtestproject.org>
To: Andrew Morton <akpm@digeo.com>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: 2.5.70-mm4
Date: 04 Jun 2003 08:55:19 -0500 [thread overview]
Message-ID: <1054734923.8311.149.camel@plars> (raw)
In-Reply-To: <20030603231827.0e635332.akpm@digeo.com>
See bug 772 - http://bugme.osdl.org/show_bug.cgi?id=772
----------------------
CC kernel/ksyms.o
kernel/ksyms.c:490: `__preempt_spin_lock' undeclared here (not in a
function)
kernel/ksyms.c:490: initializer element is not constant
kernel/ksyms.c:490: (near initialization for
`__ksymtab___preempt_spin_lock.value')
kernel/ksyms.c:491: `__preempt_write_lock' undeclared here (not in a
function)
kernel/ksyms.c:491: initializer element is not constant
kernel/ksyms.c:491: (near initialization for
`__ksymtab___preempt_write_lock.value')
make[1]: *** [kernel/ksyms.o] Error 1
make: *** [kernel] Error 2
It looks like this got broken in /include/linux/spinlock.h:
#if defined(CONFIG_SMP) && defined(CONFIG_PREEMPT) &&
!defined(CONFIG_DEBUG_EVENTLOG)
void __preempt_spin_lock(spinlock_t *lock);
void __preempt_write_lock(rwlock_t *lock);
...
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-06-04 13:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 6:18 2.5.70-mm4 Andrew Morton
2003-06-04 6:18 ` 2.5.70-mm4 Andrew Morton
2003-06-04 8:12 ` 2.5.70-mm4 RAID1 seems to work! Helge Hafting
2003-06-04 8:12 ` Helge Hafting
2003-06-04 13:55 ` Paul Larson [this message]
2003-06-04 13:55 ` 2.5.70-mm4 Paul Larson
2003-06-04 15:33 ` 2.5.70-mm4 Paul Larson
2003-06-04 15:33 ` 2.5.70-mm4 Paul Larson
2003-06-04 15:52 ` 2.5.70-mm4 Paul Larson
2003-06-04 15:52 ` 2.5.70-mm4 Paul Larson
2003-06-04 18:00 ` 2.5.70-mm4 Felipe Alfaro Solana
2003-06-04 18:00 ` 2.5.70-mm4 Felipe Alfaro Solana
2003-06-04 17:14 ` 2.5.70-mm4 Alexander Hoogerhuis
2003-06-04 17:14 ` 2.5.70-mm4 Alexander Hoogerhuis
2003-06-04 17:16 ` 2.5.70-mm4 oops jjs
2003-06-04 18:08 ` Felipe Alfaro Solana
2003-06-04 21:12 ` 2.5.70-mm4 Helge Hafting
2003-06-04 21:12 ` 2.5.70-mm4 Helge Hafting
2003-06-05 1:53 ` 2.5.70-mm4 Neil Brown
2003-06-05 1:53 ` 2.5.70-mm4 Neil Brown
2003-06-05 15:24 ` 2.5.70-mm4 this helped but still no raid0 Helge Hafting
2003-06-05 15:24 ` Helge Hafting
2003-06-04 21:33 ` 2.5.70-mm4 Rudmer van Dijk
2003-06-04 21:33 ` 2.5.70-mm4 Rudmer van Dijk
2003-06-05 9:21 ` 2.5.70-mm4 Maciej Soltysiak
2003-06-05 9:21 ` 2.5.70-mm4 Maciej Soltysiak
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=1054734923.8311.149.camel@plars \
--to=plars@linuxtestproject.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.