From: Eric Valette <eric.valette@free.fr>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.9-rc1-mm2 : compilation error in kernel/wait.c
Date: Tue, 31 Aug 2004 10:05:10 +0200 [thread overview]
Message-ID: <41343136.6080208@free.fr> (raw)
kernel/wait.c:156: error: conflicting types for '__wait_on_bit'
include/linux/wait.h:143: error: previous declaration of '__wait_on_bit'
was here
kernel/wait.c:156: error: conflicting types for '__wait_on_bit'
include/linux/wait.h:143: error: previous declaration of '__wait_on_bit'
was here
kernel/wait.c:170: error: conflicting types for '__wait_on_bit_lock'
include/linux/wait.h:144: error: previous declaration of
'__wait_on_bit_lock' was here
kernel/wait.c:170: error: conflicting types for '__wait_on_bit_lock'
include/linux/wait.h:144: error: previous declaration of
'__wait_on_bit_lock' was here
make[2]: *** [kernel/wait.o] Error 1
make[1]: *** [kernel] Error 2
--
__
/ ` Eric Valette
/-- __ o _. 6 rue Paul Le Flem
(___, / (_(_(__ 35740 Pace
Tel: +33 (0)2 99 85 26 76 Fax: +33 (0)2 99 85 26 76
E-mail: eric.valette@free.fr
next reply other threads:[~2004-08-31 8:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 8:05 Eric Valette [this message]
2004-08-31 8:09 ` 2.6.9-rc1-mm2 : compilation error in kernel/wait.c William Lee Irwin III
2004-08-31 8:14 ` William Lee Irwin III
2004-08-31 8:44 ` wait_on_bit_lock() must test_and_set_bit(), not test_bit() William Lee Irwin III
2004-08-31 21:03 ` [1/2] move wait ops' contention case completely out of line William Lee Irwin III
2004-08-31 21:05 ` [2/2] reduce number of parameters to __wait_on_bit() and __wait_on_bit_lock() William Lee Irwin III
2004-08-31 21:12 ` [3/2] document wake_up_bit()'s requirement for preceding memory barriers William Lee Irwin III
2004-08-31 8:13 ` 2.6.9-rc1-mm2 : compilation error in kernel/wait.c Andrew Morton
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=41343136.6080208@free.fr \
--to=eric.valette@free.fr \
--cc=akpm@osdl.org \
--cc=linux-kernel@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