From: "Peter Maas" <peter@7pt.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: patch-2.6.9-rc1-bk2 compile failure
Date: Thu, 26 Aug 2004 16:09:23 -0500 [thread overview]
Message-ID: <002901c48bb0$f66ab5f0$6505a8c0@pixl> (raw)
I'm guessing
static inline unsigned read_seqbegin const seqlock_t *sl)
{
unsigned ret = sl->sequence;
smp_rmb();
return ret;
}
Should Be....
static inline unsigned read_seqbegin(const seqlock_t *sl)
{
unsigned ret = sl->sequence;
smp_rmb();
return ret;
}
Peter maas
----- Original Message -----
From: "Peter Maas" <peter@7pt.net>
To: <linux-kernel@vger.kernel.org>
Sent: Thursday, August 26, 2004 4:01 PM
Subject: patch-2.6.9-rc1-bk2 compile failure
> Havent seen this posted to the LKML yet, but someone should have a quick
> answer for me.
>
> Compile failure on 2.6.9-rc1-bk2
> make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
> CHK include/linux/compile.h
> CPP arch/i386/kernel/vsyscall.lds.s
> SYSCALL arch/i386/kernel/vsyscall-int80.so
> SYSCALL arch/i386/kernel/vsyscall-sysenter.so
> AS arch/i386/kernel/vsyscall.o
> SYSCALL arch/i386/kernel/vsyscall-syms.o
> LD arch/i386/kernel/built-in.o
> CC arch/i386/lib/delay.o
> In file included from include/linux/time.h:28,
> from include/linux/timex.h:186,
> from include/linux/sched.h:11,
> from arch/i386/lib/delay.c:14:
> include/linux/seqlock.h:76: error: syntax error before "const"
> include/linux/seqlock.h:76: error: syntax error before ')' token
> make[1]: *** [arch/i386/lib/delay.o] Error 1
> make: *** [arch/i386/lib] Error 2
next reply other threads:[~2004-08-26 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 21:09 Peter Maas [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-26 21:01 patch-2.6.9-rc1-bk2 compile failure Peter Maas
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='002901c48bb0$f66ab5f0$6505a8c0@pixl' \
--to=peter@7pt.net \
--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