From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "J. Bruce Fields" <bfields@fieldses•org>
Cc: linux-next@vger•kernel.org, Bian Naimeng <biannm@cn•fujitsu.com>
Subject: linux-next: nfsd tree build warning
Date: Wed, 29 Apr 2009 13:57:02 +1000 [thread overview]
Message-ID: <20090429135702.943f2bfa.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
Hi Bruce,
Today's linux-next build (powerpc ppc64_defconfig) produced this new
warning:
fs/nfsd/nfs4state.c: In function 'EXPIRED_STATEID':
fs/nfsd/nfs4state.c:2757: warning: comparison of distinct pointer types lacks a cast
Caused by commit 78155ed75f470710f2aecb3e75e3d97107ba8374 ("nfsd4:
distinguish expired from stale stateids").
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-04-29 3:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 3:57 Stephen Rothwell [this message]
2009-04-29 15:01 ` linux-next: nfsd tree build warning J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2009-08-11 1:07 Stephen Rothwell
2009-08-11 16:53 ` J. Bruce Fields
2009-03-16 5:51 Stephen Rothwell
2009-03-16 13:42 ` J. Bruce Fields
2009-03-16 23:05 ` Stephen Rothwell
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=20090429135702.943f2bfa.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bfields@fieldses$(echo .)org \
--cc=biannm@cn$(echo .)fujitsu.com \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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