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@xxxxxxxxx> wrote: > > > On Tue, 5 Feb 2008 10:54:54 +0100 > > Haavard Skinnemoen <hskinnemoen@xxxxxxxxx> 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. - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
