From: "David B. Ritch" <dritch@hpti.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: NFS mailing list <nfs@lists.sourceforge.net>
Subject: Re: NFS_All on alpha
Date: 04 Sep 2002 11:47:06 -0400 [thread overview]
Message-ID: <1031154426.2779.19.camel@twitch> (raw)
In-Reply-To: <shs3csqr869.fsf@charged.uio.no>
Thank you. That seems to have taken care of it.
David
On Tue, 2002-09-03 at 18:59, Trond Myklebust wrote:
> >>>>> " " == David B Ritch <dritch@hpti.com> writes:
>
> > Should xdr_shift_buf take an int or a long? Are there any
>
> It should indeed take a size_t as is done in 2.5.x, and
> 2.4.20-pre5. Sorry I forgot to apply that change to my own tree.
>
> > other known problems for a 64-bit architecture in the nfs_all
> > patches?
>
> Not that I'm aware of.
>
> Cheers,
> Trond
>
> diff -Nru a/include/linux/sunrpc/xdr.h b/include/linux/sunrpc/xdr.h
> --- a/include/linux/sunrpc/xdr.h Wed Sep 4 00:58:53 2002
> +++ b/include/linux/sunrpc/xdr.h Wed Sep 4 00:58:53 2002
> @@ -138,7 +138,7 @@
> */
> extern int xdr_kmap(struct iovec *, struct xdr_buf *, unsigned int);
> extern void xdr_kunmap(struct xdr_buf *, unsigned int);
> -extern void xdr_shift_buf(struct xdr_buf *, unsigned int);
> +extern void xdr_shift_buf(struct xdr_buf *, size_t);
> extern void xdr_zero_buf(struct xdr_buf *, unsigned int);
>
> /*
--
David B. Ritch
High Performance Technologies, Inc.
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-09-04 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 21:03 NFS_All on alpha David B. Ritch
2002-09-03 22:59 ` Trond Myklebust
2002-09-04 15:47 ` David B. Ritch [this message]
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=1031154426.2779.19.camel@twitch \
--to=dritch@hpti.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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