From: WANG Cong <xiyou.wangcong@gmail.com>
To: Dave Haywood <tla@oak.selfip.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux 2.6.23-rc7 - 14 compile warnings
Date: Sat, 22 Sep 2007 10:29:32 +0800 [thread overview]
Message-ID: <20070922022932.GC2480@hacking> (raw)
In-Reply-To: <46F39004.4050106@oak.selfip.net>
On Fri, Sep 21, 2007 at 10:33:56AM +0100, Dave Haywood wrote:
>Contents:
> ver_linux output
> Summary of compile warnings
> Full compile log
> .config
>
>============================
>
>Linux s1 2.6.23-rc7-g335fb8fc #9 SMP Fri Sep 21 09:31:01 BST 2007 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux
>
>Gnu C 4.2.0
>Gnu make 3.81
>binutils 2.17
>util-linux 2.12r
>mount 2.12r
>module-init-tools 3.2.2
>e2fsprogs 1.40.2
>PPP 2.4.4
>Linux C Library 2.5
>Dynamic linker (ldd) 2.5
>Procps 3.2.7
>Net-tools 1.60
>Kbd 1.12
>Sh-utils 6.9
>udev 114
>
>============================
>
>Summary:
> CC mm/slub.o
>mm/slub.c: In function 'kfree':
>mm/slub.c:2491: warning: passing argument 3 of 'slab_free' discards
>qualifiers from pointer target type
>
> CC fs/autofs4/symlink.o
>fs/autofs4/symlink.c: In function 'autofs4_follow_link':
>fs/autofs4/symlink.c:18: warning: passing argument 2 of 'nd_set_link'
>discards qualifiers from pointer target type
These two warnings are suspicious. Explicit casts are already there, how
they come out? Or gcc bugs?
{snip}
next prev parent reply other threads:[~2007-09-22 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 9:33 linux 2.6.23-rc7 - 14 compile warnings Dave Haywood
2007-09-22 2:29 ` WANG Cong [this message]
2007-09-23 2:23 ` Gerhard Mack
2007-09-23 3:14 ` WANG Cong
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=20070922022932.GC2480@hacking \
--to=xiyou.wangcong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tla@oak.selfip.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.