linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mike Sager <sager@netapp.com>
Subject: linux-next: nfs tree build warning
Date: Fri, 19 Jun 2009 10:50:22 +1000	[thread overview]
Message-ID: <20090619105022.4dc10679.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]

Hi Trond,

Today's linux-next build (powerpc ppc64_defconfig) produced this warning:

fs/nfs/super.c: In function 'nfs_parse_mount_options':
fs/nfs/super.c:1253: warning: passing argument 2 of 'match_int' from incompatible pointer type
include/linux/parser.h:29: note: expected 'int *' but argument is of type 'long unsigned int *'

Introduced by commit 3fd5be9e19921a89d9ed78d6a708a379a6c3c76a ("nfs41:
add mount command option minorversion").

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-06-19  0:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19  0:50 Stephen Rothwell [this message]
2009-06-19  1:09 ` linux-next: nfs tree build warning Trond Myklebust
2009-06-19  2:00   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-12-31  0:01 Stephen Rothwell
2009-08-10  0:58 Stephen Rothwell
2009-08-10 12:51 ` Trond Myklebust
2009-05-01  3:15 Stephen Rothwell
2009-05-01  3:22 ` Trond Myklebust
2009-05-01 12:19   ` Benny Halevy
2009-05-01 14:56     ` William A. (Andy) Adamson
2009-06-09  9:13 ` 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=20090619105022.4dc10679.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sager@netapp.com \
    --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;
as well as URLs for NNTP newsgroup(s).