From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Nuno Monteiro <nuno@itsari.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: rwsem-spinlock error
Date: Thu, 17 Jun 2004 20:35:36 +1000 [thread overview]
Message-ID: <40D173F8.4060701@yahoo.com.au> (raw)
In-Reply-To: <Pine.GSO.4.58.0406171206470.22919@waterleaf.sonytel.be>
Geert Uytterhoeven wrote:
> On Wed, 16 Jun 2004, Marcelo Tosatti wrote:
>
>><nickpiggin:yahoo.com.au>:
>> o rwsem race fixes backported from 2.6
>
>
>>Nuno Monteiro:
>> o Fix rwsem-fix typo
>> o Complete rwsem typo fix
>
>
> | rwsem-spinlock.c: In function `__rwsem_wake_one_writer':
> | rwsem-spinlock.c:111: `tsk' undeclared (first use in this function)
> | rwsem-spinlock.c:111: (Each undeclared identifier is reported only once
> | rwsem-spinlock.c:111: for each function it appears in.)
>
> How can this ever compile on any architecture?
>
Dangit. rwsem-spinlock.c isn't compiled for many architectures.
It should just require a
struct task_struct *tsk;
sorry.
next prev parent reply other threads:[~2004-06-17 10:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 18:33 Linux 2.4.27-pre6 Marcelo Tosatti
2004-06-17 9:40 ` Linux 2.4.27-pre6: visor.c Eyal Lebedinsky
2004-06-17 9:48 ` Linux 2.4.27-pre6: visor.c (patch) Eyal Lebedinsky
2004-06-17 10:06 ` ip6_tables warning (was: Re: Linux 2.4.27-pre6) Geert Uytterhoeven
2004-06-17 10:13 ` ip6_tables warning YOSHIFUJI Hideaki / 吉藤英明
2004-06-17 17:12 ` David S. Miller
2004-06-17 19:05 ` igmp warning (was: Re: Linux 2.4.27-pre6) Geert Uytterhoeven
2004-06-17 19:09 ` David S. Miller
2004-06-17 10:10 ` rwsem-spinlock error " Geert Uytterhoeven
2004-06-17 10:35 ` Nick Piggin [this message]
2004-06-17 13:13 ` rwsem-spinlock error Nuno Monteiro
2004-06-17 13:01 ` Linux 2.4.27-pre6 Andreas Haumer
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=40D173F8.4060701@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=nuno@itsari.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.