On Thu, 28 Jul 2005 16:02:58 +0100 Christoph Hellwig <[EMAIL PROTECTED]> wrote:
>
> > And where were you a week ago when I asked if I should post this patch?
>
> A :-) Can't remember it at all, maybe you forgot that we mere mortals can't
> read linux-arch@vger.kernel.org ?
Sorry about that, my o
> And where were you a week ago when I asked if I should post this patch?
A :-) Can't remember it at all, maybe you forgot that we mere mortals can't
read linux-arch@vger.kernel.org ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROT
On Fri, Jul 29, 2005 at 01:13:07AM +1000, Stephen Rothwell wrote:
> On Thu, 28 Jul 2005 16:02:58 +0100 Christoph Hellwig <[EMAIL PROTECTED]>
> wrote:
> >
> > > And where were you a week ago when I asked if I should post this patch?
> >
> > A :-) Can't remember it at all, maybe you forgot that we
On Fri, 29 Jul 2005 00:48:38 +1000 Stephen Rothwell <[EMAIL PROTECTED]> wrote:
>
> readv/writev were done ages ago (since they are necessary for other
But you are right, compat_sys_readv/writev need adjusting to call the
compat_read/write method if they exist ...
--
Cheers,
Stephen Rothwell
On Thu, 28 Jul 2005 15:16:53 +0100 Christoph Hellwig <[EMAIL PROTECTED]> wrote:
>
> This looks totally horrible, especially as we'd need readv/writev and
> pread/pwrite aswell. I don't think anyone but Andi actually liked this
> approach when discussed earlier.
readv/writev were done ages ago (si
On Thu, Jul 28, 2005 at 11:43:41PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Someone mentioned the mess in evdev.c that is caused by the fact that the
> structures that are passed to/from user mode via read/write require
> conversion when this API is used from 32 bit tasks on 64 bit kernels.
>
6 matches
Mail list logo
