From: Eric Paris <eparis@parisplace•org>
To: Dave Chinner <david@fromorbit•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Eric Paris <eparis@redhat•com>, Al Viro <viro@zeniv•linux.org.uk>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
xfs@oss•sgi.com
Subject: Re: linux-next: vfs/fsnotify trees build warning
Date: Mon, 8 Feb 2010 13:01:46 -0500 [thread overview]
Message-ID: <7e0fb38c1002081001y111bd0a2p40a8a896b0668d13@mail.gmail.com> (raw)
In-Reply-To: <20100125042925.GM25842@discord.disaster>
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....
-Eric
next prev parent reply other threads:[~2010-02-08 18:01 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 [this message]
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=7e0fb38c1002081001y111bd0a2p40a8a896b0668d13@mail.gmail.com \
--to=eparis@parisplace$(echo .)org \
--cc=david@fromorbit$(echo .)com \
--cc=eparis@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=xfs@oss$(echo .)sgi.com \
/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