From: Trond Myklebust <trond.myklebust@fys•uio.no>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Mike Sager <sager@netapp•com>
Subject: Re: linux-next: nfs tree build warning
Date: Thu, 18 Jun 2009 18:09:12 -0700 [thread overview]
Message-ID: <1245373752.8756.59.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20090619105022.4dc10679.sfr@canb.auug.org.au>
On Fri, 2009-06-19 at 10:50 +1000, Stephen Rothwell wrote:
> 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").
>
That's my fault: it was due to inattention during the merge of the
nfsv41 tree with the mainline NFS changes. I'll fix...
Trond
next prev parent reply other threads:[~2009-06-19 1:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 0:50 linux-next: nfs tree build warning Stephen Rothwell
2009-06-19 1:09 ` Trond Myklebust [this message]
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=1245373752.8756.59.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys$(echo .)uio.no \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sager@netapp$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/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