From: David Howells <dhowells@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linuxppc-dev@ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>,
sam@ravnborg.org, linux-kernel@vger.kernel.org,
rmk@arm.linux.org.uk
Subject: Re: [PATCH] Complain about missing system calls.
Date: Tue, 20 Mar 2007 10:51:33 +0000 [thread overview]
Message-ID: <11422.1174387893@redhat.com> (raw)
In-Reply-To: <1174376588.3392.168.camel@pmac.infradead.org>
David Woodhouse <dwmw2@infradead.org> wrote:
> > hm, did you try running this on x86_64?
>
> I don't have any. I only tested it on PowerPC and i386. Others then
> provided more exclusions for SPARC and maybe ARM, although I'm not sure
> you have the latter yet. It's not hard to add extra exclusions.
You could always have asked to borrow my test box.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@ozlabs.org, sam@ravnborg.org,
linux-kernel@vger.kernel.org, rmk@arm.linux.org.uk
Subject: Re: [PATCH] Complain about missing system calls.
Date: Tue, 20 Mar 2007 10:51:33 +0000 [thread overview]
Message-ID: <11422.1174387893@redhat.com> (raw)
In-Reply-To: <1174376588.3392.168.camel@pmac.infradead.org>
David Woodhouse <dwmw2@infradead.org> wrote:
> > hm, did you try running this on x86_64?
>
> I don't have any. I only tested it on PowerPC and i386. Others then
> provided more exclusions for SPARC and maybe ARM, although I'm not sure
> you have the latter yet. It's not hard to add extra exclusions.
You could always have asked to borrow my test box.
David
next prev parent reply other threads:[~2007-03-20 10:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 23:01 [PATCH] Complain about missing system calls David Woodhouse
2007-03-09 0:14 ` David Miller
2007-03-09 0:14 ` David Miller
2007-03-09 0:18 ` David Woodhouse
2007-03-09 0:18 ` David Woodhouse
2007-03-20 12:12 ` Sam Ravnborg
2007-03-20 12:12 ` Sam Ravnborg
2007-03-09 3:31 ` Anton Blanchard
2007-03-09 3:31 ` Anton Blanchard
2007-03-09 8:43 ` Russell King
2007-03-09 8:43 ` Russell King
2007-03-09 16:11 ` Andi Kleen
2007-03-09 16:11 ` Andi Kleen
2007-03-09 16:38 ` Jan-Benedict Glaw
2007-03-09 16:38 ` Jan-Benedict Glaw
2007-03-09 19:00 ` Andi Kleen
2007-03-09 19:35 ` Jan-Benedict Glaw
2007-03-09 19:35 ` Jan-Benedict Glaw
2007-03-10 9:58 ` Martin Schwidefsky
2007-03-10 9:58 ` Martin Schwidefsky
2007-03-09 19:40 ` H. Peter Anvin
2007-03-09 20:13 ` Russell King
2007-03-09 20:13 ` Russell King
2007-03-09 20:52 ` H. Peter Anvin
2007-03-09 16:47 ` Benjamin Herrenschmidt
2007-03-09 16:47 ` Benjamin Herrenschmidt
2007-03-09 18:54 ` Andi Kleen
2007-03-09 18:54 ` Andi Kleen
2007-03-10 9:51 ` Martin Schwidefsky
2007-03-10 9:51 ` Martin Schwidefsky
2007-03-09 17:20 ` David Woodhouse
2007-03-09 17:20 ` David Woodhouse
2007-03-19 23:42 ` Andrew Morton
2007-03-19 23:42 ` Andrew Morton
2007-03-20 7:43 ` David Woodhouse
2007-03-20 7:43 ` David Woodhouse
2007-03-20 10:51 ` David Howells [this message]
2007-03-20 10:51 ` David Howells
2007-03-20 10:56 ` Russell King
2007-03-20 10:56 ` Russell King
2007-03-21 11:25 ` David Woodhouse
2007-03-21 11:25 ` David Woodhouse
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=11422.1174387893@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rmk@arm.linux.org.uk \
--cc=sam@ravnborg.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.