From: Paul Mundt <lethal@linux-sh.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>,
torvalds@linux-foundation.org, davidel@xmailserver.org,
David Howells <dhowells@redhat.com>,
linux-arch@vger.kernel.org, mtk-manpages@gmx.net,
tglx@linutronix.de, Hirokazu Takata <takata@linux-m32r.org>
Subject: Re: [PATCH] Fix timerfd breakage on avr32
Date: Tue, 5 Feb 2008 19:26:44 +0900 [thread overview]
Message-ID: <20080205102644.GA5038@linux-sh.org> (raw)
In-Reply-To: <20080205021347.4785ca44.akpm@linux-foundation.org>
On Tue, Feb 05, 2008 at 02:13:47AM -0800, Andrew Morton wrote:
> On Tue, 5 Feb 2008 11:03:47 +0100 Haavard Skinnemoen <hskinnemoen@atmel.com> wrote:
>
> > On Tue, 5 Feb 2008 10:54:54 +0100
> > Haavard Skinnemoen <hskinnemoen@atmel.com> wrote:
> >
> > > The next time you go and remove a system call, could you _please_ post
> > > a HUGE warning to linux-arch? Or just do a quick grep and fix it up.
> >
> > Btw, a quick grep through 2.6.24-mm1 shows
> >
> > arch/frv/kernel/entry.S: .long sys_timerfd
> > arch/m32r/kernel/syscall_table.S: .long sys_timerfd
> > arch/sh/kernel/syscalls_32.S: .long sys_timerfd
> > arch/sh/kernel/syscalls_64.S: .long sys_timerfd /* 350 */
> >
> > so frv, m32r and sh are probably broken too.
> >
>
> argh. After fixing so many architectures I asked for a grepped
> fix :(
>
>
> This?
>
At least if this patch goes in first then bisect won't needlessly break,
though the previous patch has already gone to Linus, so maybe it's too
late already. Once this patch and the previous one are in, then the new
interface can be wired up -- preferably in that order.
next prev parent reply other threads:[~2008-02-05 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 6:27 [patch 012/265] timerfd: wire the new timerfd API to the x86 family akpm
2008-02-05 9:54 ` [PATCH] Fix timerfd breakage on avr32 Haavard Skinnemoen
2008-02-05 10:03 ` Haavard Skinnemoen
2008-02-05 10:13 ` Andrew Morton
2008-02-05 10:26 ` Paul Mundt [this message]
2008-02-06 11:04 ` Russell King
2008-02-06 11:12 ` Heiko Carstens
2008-02-06 13:00 ` Geert Uytterhoeven
2008-02-06 16:18 ` Randy Dunlap
2008-02-06 17:04 ` Davide Libenzi
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=20080205102644.GA5038@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=dhowells@redhat.com \
--cc=hskinnemoen@atmel.com \
--cc=linux-arch@vger.kernel.org \
--cc=mtk-manpages@gmx.net \
--cc=takata@linux-m32r.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).