From: Christoph Hellwig <hch@infradead.org>
To: Eric Paris <eparis@parisplace.org>
Cc: Dave Chinner <david@fromorbit.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org, Eric Paris <eparis@redhat.com>,
xfs@oss.sgi.com, linux-next@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: linux-next: vfs/fsnotify trees build warning
Date: Mon, 8 Feb 2010 14:36:58 -0500 [thread overview]
Message-ID: <20100208193658.GA9527@infradead.org> (raw)
In-Reply-To: <7e0fb38c1002081001y111bd0a2p40a8a896b0668d13@mail.gmail.com>
On Mon, Feb 08, 2010 at 01:01:46PM -0500, Eric Paris wrote:
> On Sun, Jan 24, 2010 at 11:29 PM, Dave Chinner <david@fromorbit.com> wrote:
> > On Mon, Jan 25, 2010 at 03:04:56PM +1100, Stephen Rothwell wrote:
> >> Hi Eric, Al,
> >>
> >> Today's linux-next build (x86_64 allmodconfig) produced these warnings:
>
> I just switched fsnotify to use const unsigned char * so hopefully
> they will shut up tomorrow....
The xfs tree is also about to get a patch to turn off -Wpointer-sign
again. If it was up to me we should turn it on for the whole build,
we'll just need good way to deal with static initializers and strlen,
but some simple wrappers might do it for those.
prev parent reply other threads:[~2010-02-08 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 4:04 linux-next: vfs/fsnotify trees build warning Stephen Rothwell
2010-01-25 4:16 ` Stephen Rothwell
2010-01-25 4:29 ` Dave Chinner
2010-02-08 18:01 ` Eric Paris
2010-02-08 19:36 ` Christoph Hellwig [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=20100208193658.GA9527@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=eparis@parisplace.org \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
--cc=xfs@oss.sgi.com \
/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).