Linux NFS development
 help / color / mirror / Atom feed
From: Tom Tucker <tom@opengridcomputing.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [RFC,PATCH 0/8] RDMA Transport Provider
Date: Fri, 30 Nov 2007 14:50:03 -0600	[thread overview]
Message-ID: <1196455803.5432.45.camel@trinity.ogc.int> (raw)
In-Reply-To: <20071130171649.GC14943@fieldses.org>


On Fri, 2007-11-30 at 12:16 -0500, J. Bruce Fields wrote:
> On Fri, Nov 30, 2007 at 09:59:28AM -0600, Tom Tucker wrote:
> >=20

[...snip...]

> Thanks!  Applied and pushed out.
>=20

thank you too.

> >=20
> > > I still need the following to get it to compile.  Also, I'm getti=
ng
> > > these warnings:
> > >=20

So here's an irony for you... if you're on a 32 bit x86 platform you ge=
t
this definition for test_and_clear_bit:

*** include/asm-x86/bitops_32.h:
test_and_clear_bit[222]        static inline int test_and_clear_bit(int=
 nr, volatile unsigned long * addr)

which will give you an error if you use &int, but if you're on a 64b x8=
6 platform,
you get this definition:

*** include/asm-x86/bitops_64.h:
test_and_clear_bit[211]        static inline int test_and_clear_bit(int=
 nr, volatile void *addr)

That's why I didn't see the warning, because the parameter type on a 64=
b
system is void *.  This looks like a bug to me, but maybe someone can
explain the reasoning?

> > > net/sunrpc/svc_rdma_transport.c: In function =E2=80=98dto_tasklet=
_func=E2=80=99:
> > > net/sunrpc/svc_rdma_transport.c:232: warning: passing argument 2 =
of =E2=80=98test_and_clear_bit=E2=80=99 from incompatible pointer type
> > > net/sunrpc/svc_rdma_transport.c:241: warning: passing argument 2 =
of =E2=80=98constant_test_bit=E2=80=99 from incompatible pointer type
> > > net/sunrpc/svc_rdma_transport.c:241: warning: passing argument 2 =
of =E2=80=98variable_test_bit=E2=80=99 from incompatible pointer type
> > > net/sunrpc/svc_rdma_transport.c:245: warning: passing argument 2 =
of =E2=80=98test_and_clear_bit=E2=80=99 from incompatible pointer type
> > > net/sunrpc/svc_rdma_transport.c: In function =E2=80=98rq_comp_han=
dler=E2=80=99:
> > > net/sunrpc/svc_rdma_transport.c:271: warning: passing argument 2 =
of =E2=80=98set_bit=E2=80=99 from incompatible pointer type
> > > net/sunrpc/svc_rdma_transport.c: In function =E2=80=98sq_comp_han=
dler=E2=80=99:
> > > net/sunrpc/svc_rdma_transport.c:382: warning: passing argument 2 =
of =E2=80=98set_bit=E2=80=99 from incompatible pointer type
> > > net/sunrpc/svc_rdma_transport.c: In function =E2=80=98rdma_cma_ha=
ndler=E2=80=99:
> > > net/sunrpc/svc_rdma_transport.c:617: warning: passing argument 2 =
of =E2=80=98clear_bit=E2=80=99 from incompatible pointer type
> > > net/sunrpc/svc_rdma_transport.c: In function =E2=80=98svc_rdma_ac=
cept=E2=80=99:
> > > net/sunrpc/svc_rdma_transport.c:848: warning: passing argument 2 =
of =E2=80=98set_bit=E2=80=99 from incompatible pointer type
> > >=20
> >=20
> > I'm mystified as to why I didn't get these warnings. I built on a 6=
4 bit
> > machine. It seems like that would give the warning since unsigned l=
ong
> > isn't even the same size as int.
>=20
> Yeah, I can't see how any compiler could miss that.  How do you usual=
ly
> build?
>=20
> --b.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" =
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      parent reply	other threads:[~2007-11-30 20:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 22:44 [RFC,PATCH 0/8] RDMA Transport Provider Tom Tucker
     [not found] ` <20071129224412.14887.14136.stgit-gUwIgmpLGaKNDNWfRnPdfg@public.gmane.org>
2007-11-29 22:45   ` [RFC,PATCH 1/8] rdma: SVCRMDA Header File Tom Tucker
2007-11-29 22:45   ` [RFC,PATCH 2/8] rdma: SVCRDMA Transport Module Tom Tucker
2007-11-29 22:45   ` [RFC,PATCH 3/8] rdma: SVCRDMA Core Transport Services Tom Tucker
2007-11-29 22:45   ` [RFC,PATCH 4/8] rdma: SVCRDMA recvfrom Tom Tucker
2007-11-29 22:45   ` [RFC,PATCH 5/8] rdma: SVCRDMA sendto Tom Tucker
2007-11-29 22:45   ` [RFC,PATCH 6/8] rdma: ONCRPC RDMA protocol marshalling Tom Tucker
2007-11-29 22:45   ` [RFC,PATCH 7/8] rdma: makefile Tom Tucker
     [not found]     ` <20071129224513.14887.8074.stgit-gUwIgmpLGaKNDNWfRnPdfg@public.gmane.org>
2007-12-03 17:00       ` Chuck Lever
2007-12-03 17:24         ` Tom Tucker
     [not found]           ` <1196702699.5811.0.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2007-12-03 17:25             ` J. Bruce Fields
2007-12-03 17:26         ` Tom Tucker
2007-12-03 17:08       ` [RFC,PATCH 7/8] rdma: makefile (second thread) Chuck Lever
2007-12-03 20:29         ` James Lentini
     [not found]           ` <Pine.LNX.4.64.0712031524250.7142-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
2007-12-03 20:52             ` Chuck Lever
2007-12-03 22:29               ` James Lentini
     [not found]                 ` <Pine.LNX.4.64.0712031656150.7142-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
2007-12-04  0:52                   ` Chuck Lever
2007-12-04 23:04                     ` James Lentini
     [not found]                       ` <Pine.LNX.4.64.0712041800270.7142-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
2007-12-05  3:08                         ` Chuck Lever
2007-11-29 22:45   ` [RFC,PATCH 8/8] rdma: Kconfig Tom Tucker
2007-11-30  4:45   ` [RFC,PATCH 0/8] RDMA Transport Provider J. Bruce Fields
2007-11-30 15:59     ` Tom Tucker
     [not found]       ` <1196438368.5432.10.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2007-11-30 17:16         ` J. Bruce Fields
2007-11-30 19:41           ` Tom Tucker
     [not found]             ` <1196451693.5432.35.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2007-11-30 20:48               ` Chuck Lever
2007-11-30 20:50           ` Tom Tucker [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=1196455803.5432.45.camel@trinity.ogc.int \
    --to=tom@opengridcomputing.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox