From: Arnd Bergmann <arnd@arndb.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>,
linuxppc-dev@ozlabs.org, torvalds@osdl.org,
Paul Mackerras <paulus@samba.org>,
davem@davemloft.net
Subject: Re: [PATCH] sys_vmsplice
Date: Fri, 21 Apr 2006 12:41:35 +0200 [thread overview]
Message-ID: <200604211241.36596.arnd@arndb.de> (raw)
In-Reply-To: <20060421022555.2d460805.akpm@osdl.org>
On Friday 21 April 2006 11:25, Andrew Morton wrote:
> It might be better to just stick the new entry into the spufs table, make
> sure that the powerpc guys see it go in. That way, ppc64 people (Linus,
> maybe you?) can test it.
>
> I guess mapping it onto sys_ni_syscall would be safest.
>
> (It's been broken since sys_tee went in, btw).
The BUILD_BUG_ON in there was just overkill. How about if we just add a
small comment to the systbl on powerpc to remind people about the fact
that there is another file to edit? Patch follows.
Arnd <><
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Jens Axboe <axboe@suse.de>,
linux-kernel@vger.kernel.org, torvalds@osdl.org,
davem@davemloft.net, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] sys_vmsplice
Date: Fri, 21 Apr 2006 12:41:35 +0200 [thread overview]
Message-ID: <200604211241.36596.arnd@arndb.de> (raw)
In-Reply-To: <20060421022555.2d460805.akpm@osdl.org>
On Friday 21 April 2006 11:25, Andrew Morton wrote:
> It might be better to just stick the new entry into the spufs table, make
> sure that the powerpc guys see it go in. That way, ppc64 people (Linus,
> maybe you?) can test it.
>
> I guess mapping it onto sys_ni_syscall would be safest.
>
> (It's been broken since sys_tee went in, btw).
The BUILD_BUG_ON in there was just overkill. How about if we just add a
small comment to the systbl on powerpc to remind people about the fact
that there is another file to edit? Patch follows.
Arnd <><
next prev parent reply other threads:[~2006-04-21 10:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 8:02 [PATCH] sys_vmsplice Jens Axboe
2006-04-21 9:17 ` Andrew Morton
2006-04-21 9:21 ` Jens Axboe
2006-04-21 9:25 ` Andrew Morton
2006-04-21 9:52 ` Jens Axboe
2006-04-21 10:41 ` Arnd Bergmann [this message]
2006-04-21 10:41 ` Arnd Bergmann
2006-04-21 10:45 ` [PATCH] fix spu_callbacks BUILD_BUG_ON Arnd Bergmann
2006-04-21 10:45 ` Arnd Bergmann
2006-04-21 13:14 ` Jan Engelhardt
2006-04-21 13:14 ` Jan Engelhardt
2006-04-21 13:52 ` Arnd Bergmann
2006-04-21 13:52 ` Arnd Bergmann
2006-04-21 20:45 ` [PATCH] sys_vmsplice Linus Torvalds
2006-04-21 21:01 ` Jens Axboe
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=200604211241.36596.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=torvalds@osdl.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.