From: Andrew Morton <akpm@osdl.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-arch@vger.kernel.org, JANAK DESAI <janak@us.ibm.com>,
Ulrich Drepper <drepper@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
David Howells <dhowells@redhat.com>,
Davide Libenzi <davidel@xmailserver.org>,
Christoph Lameter <christoph@lameter.com>
Subject: Re: new syscalls
Date: Wed, 18 Jan 2006 13:36:29 -0800 [thread overview]
Message-ID: <20060118133629.1cda96fd.akpm@osdl.org> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F05737A9F@scsmsx401.amr.corp.intel.com>
"Luck, Tony" <tony.luck@intel.com> wrote:
>
> > Various new syscalls which are trickling their way Linuswards and will need
> > testing and wiring up once they get there:
>
> Are there test-suites for any/all of these new calls?
>
That's an excellent point.
Guys, architecture maintainers need test suites to verify that the syscalls
actually work as they wire them up. Please share. A stable URL would be
preferred - something which can go into the changlog or conceivably into
the kernel source.
Thanks.
next prev parent reply other threads:[~2006-01-18 21:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 18:55 new syscalls Luck, Tony
2006-01-18 21:36 ` Andrew Morton [this message]
2006-01-18 21:48 ` Ulrich Drepper
2006-01-18 21:58 ` David S. Miller
2006-01-18 21:53 ` David Woodhouse
2006-01-18 21:58 ` David S. Miller
2006-01-20 10:04 ` Andi Kleen
2006-01-20 10:15 ` David S. Miller
2006-01-23 6:44 ` David Woodhouse
2006-01-23 9:58 ` Heiko Carstens
2006-01-19 1:17 ` Davide Libenzi
2006-01-19 1:26 ` David S. Miller
2006-01-19 5:00 ` David Woodhouse
2006-01-19 1:28 ` Andrew Morton
2006-01-19 21:48 ` Davide Libenzi
2006-01-20 0:13 ` Davide Libenzi
2006-01-20 0:23 ` Ulrich Drepper
2006-01-20 0:34 ` Davide Libenzi
2006-01-19 1:19 ` Christoph Lameter
2006-01-19 2:30 ` Andi Kleen
2006-01-19 13:50 ` JANAK DESAI
2006-01-22 17:45 ` JANAK DESAI
2006-01-24 23:44 ` JANAK DESAI
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 3:29 Andrew Morton
2006-01-18 3:38 ` Andi Kleen
2006-01-20 9:43 ` Heiko Carstens
2006-01-20 9:48 ` Andi Kleen
2006-01-20 9:49 ` David S. Miller
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=20060118133629.1cda96fd.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=christoph@lameter.com \
--cc=davidel@xmailserver.org \
--cc=dhowells@redhat.com \
--cc=drepper@redhat.com \
--cc=dwmw2@infradead.org \
--cc=janak@us.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=tony.luck@intel.com \
/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