From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Paris <eparis@redhat.com>, Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: vfs/fsnotify trees build warning
Date: Mon, 25 Jan 2010 15:16:17 +1100 [thread overview]
Message-ID: <20100125151617.4a91ad17.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100125150456.c796f0b0.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Hi Eric, Al,
On Mon, 25 Jan 2010 15:04:56 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next build (x86_64 allmodconfig) produced these warnings:
These warnings only appear after I merge the fsnotify tree into
linux-next. The vfs tree has been merged much earlier. So at least the
first of these is introduced by a vfs tree commit
(82a1dff3ed894a3b453474f168d55381a1e7318c "Lose the new_name argument of
fsnotify_move()") but only exposed by the merge of the fsnotify tree.
> In file included from include/linux/security.h:26,
> from fs/xfs/linux-2.6/xfs_iops.c:56:
> include/linux/fsnotify.h: In function 'fsnotify_move':
> include/linux/fsnotify.h:87: warning: pointer targets in initialization differ in signedness
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-25 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 4:04 Stephen Rothwell
2010-01-25 4:16 ` Stephen Rothwell [this message]
2010-01-25 4:29 ` Dave Chinner
2010-02-08 18:01 ` Eric Paris
2010-02-08 19:36 ` Christoph Hellwig
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=20100125151617.4a91ad17.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®