From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Eric Paris <eparis@redhat.com>,
viro@zeniv.linux.org.uk, hch@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] notification: including fanotify
Date: Sun, 28 Feb 2010 10:29:37 +1100 [thread overview]
Message-ID: <20100228102937.cac7dc55.sfr@canb.auug.org.au> (raw)
In-Reply-To: <alpine.LFD.2.00.1002271331570.4513@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
Hi Linus,
On Sat, 27 Feb 2010 13:33:21 -0800 (PST) Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> On Sat, 27 Feb 2010, Linus Torvalds wrote:
> >
> > (b) the compile has obviously never been tested with any modern gcc
> > version. I get tons of warnings after the pull, like
>
> In fact, this seems to be due to a commit that explicitly says:
>
> I do not add -Wpointer-sign to the fsnotify
> code as there are still issues with kstrdup and strlen which would pop
> out needless warnings.
>
> but then the patch actually has
>
> --- a/fs/notify/Makefile
> +++ b/fs/notify/Makefile
> @@ -1,3 +1,5 @@
> +EXTRA_CFLAGS += -Wpointer-sign
> +
>
> WTF? Which part of this was tested AT ALL? Clearly there was not even a
> compile test going on.
You also forgot to mention that this whole tree has been rebased since
(my) Friday and the version of the above commit in linux-next does not
have that hunk.
As that commit does say, these warnings first came to light when the xfs
tree added that flag to its build. It was removed again after a couple of
days because it generates quite a few warnings (as you have seen). It
appears that thee needs to be more cleanup before it is enabled again.
--
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-02-27 23:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 21:14 Eric Paris
2010-02-27 21:29 ` Linus Torvalds
2010-02-27 21:33 ` Linus Torvalds
2010-02-27 23:29 ` Stephen Rothwell [this message]
2010-02-27 23:38 ` Linus Torvalds
2010-02-27 22:51 ` Al Viro
2010-02-27 23:49 ` Eric Paris
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=20100228102937.cac7dc55.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=eparis@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®