From: Arnd Bergmann <arnd@arndb•de>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Michael Kerrisk <mtk-manpages@gmx•net>,
linux-kernel@vger•kernel.org,
Kamalesh Babulal <kamalesh@linux•vnet.ibm.com>,
linuxppc-dev@ozlabs•org, Paul Mackerras <paulus@samba•org>,
Davide Libenzi <davidel@xmailserver•org>,
Balbir Singh <balbir@linux•vnet.ibm.com>
Subject: Re: 2.6.24-rc3-mm2 - Build Failure on powerpc timerfd() undeclared
Date: Thu, 29 Nov 2007 01:57:51 +0100 [thread overview]
Message-ID: <200711290157.52487.arnd@arndb.de> (raw)
In-Reply-To: <20071128104345.9474025e.akpm@linux-foundation.org>
On Wednesday 28 November 2007 19:43:45 Andrew Morton wrote:
> > I guess all architectures except x86 are currently broken because they
> > reference the old sys_timerfd function.
>
> None of them were broken in my testing and I'm unsure why powerpc broke
> here.
PowerPC is unique in that it actually relies on the declarations
in include/{linux,asm}/syscalls.h to be present, because the
spu_syscall_table is generated from C code, not from assembly.
One reason why I did this was to be sure to find this exact
type of problem at compile-time, not at link time.
Arnd <><
next prev parent reply other threads:[~2007-11-29 1:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071128034140.648383f0.akpm@linux-foundation.org>
2007-11-28 12:40 ` 2.6.24-rc3-mm2 - Build Failure on powerpc timerfd() undeclared Kamalesh Babulal
2007-11-28 13:32 ` Arnd Bergmann
2007-11-28 18:43 ` Andrew Morton
2007-11-28 19:25 ` Davide Libenzi
2007-11-29 0:57 ` Arnd Bergmann [this message]
2007-11-28 14:33 ` [BUG] 2.6.24-rc3-mm2 soft lockup while running tbench Kamalesh Babulal
2007-11-29 21:09 ` Andrew Morton
2007-11-30 5:09 ` Kamalesh Babulal
2007-11-29 9:00 ` [BUG] 2.6.24-rc3-mm2 kernel bug on nfs & cifs mounted partitions Kamalesh Babulal
2007-11-29 9:09 ` Andrew Morton
2007-11-29 11:57 ` Kamalesh Babulal
2007-11-29 12:10 ` Jan Kara
2007-11-29 14:36 ` Kamalesh Babulal
2007-11-29 14:40 ` Jan Kara
2007-12-02 15:55 ` Kamalesh Babulal
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=200711290157.52487.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=akpm@linux-foundation$(echo .)org \
--cc=balbir@linux$(echo .)vnet.ibm.com \
--cc=davidel@xmailserver$(echo .)org \
--cc=kamalesh@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mtk-manpages@gmx$(echo .)net \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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