From: Andrew Morton <akpm@osdl.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] add -Werror-implicit-function-declaration to CFLAGS
Date: Wed, 23 Nov 2005 15:50:35 -0800 [thread overview]
Message-ID: <20051123155035.2494a746.akpm@osdl.org> (raw)
In-Reply-To: <20051123233853.GL3963@stusta.de>
Adrian Bunk <bunk@stusta.de> wrote:
>
> On Wed, Nov 23, 2005 at 03:09:05PM -0800, Andrew Morton wrote:
> > Adrian Bunk <bunk@stusta.de> wrote:
> > >
> > > Currently, using an undeclared function gives a compile warning, but it
> > > can lead to a nasty runtime error if the prototype of the function is
> > > different from what gcc guessed.
> > >
> > > With -Werror-implicit-function-declaration, we are getting an immediate
> > > compile error instead.
> >
> > Where "we" == "me". This patch means I get to fix all the errors which I
> > encounter. No fair. This should be the last patch, not the first.
>
> Is it my fault that you applied neither Al Viro's patches to remove the
> usages of the ISA legacy functions
Never saw them.
> nor my patch to mark
> virt_to_bus/bus_to_virt as __deprecated on i386?
That won't make powerpc compile.
Plus there are various other unfixed functions around the tree with various
.configs.
It took about four releases to teach people that the jsm driver won't
compile. I don't want to go adding things to -mm which break it in this
way - that causes us to lose testers.
The patch is a good one, but it should come last.
next prev parent reply other threads:[~2005-11-23 23:51 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 22:34 Adrian Bunk
2005-11-23 23:09 ` Andrew Morton
2005-11-23 23:38 ` Adrian Bunk
2005-11-23 23:50 ` Andrew Morton [this message]
2005-11-24 0:13 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2006-07-07 17:10 Luck, Tony
2006-07-06 16:37 Adrian Bunk
2006-07-06 18:05 ` Jesper Juhl
2006-07-06 18:20 ` Dave Jones
2006-07-07 3:36 ` Sam Ravnborg
2006-07-07 5:02 ` Valdis.Kletnieks
2006-07-07 6:42 ` Sam Ravnborg
2006-07-07 7:49 ` Adrian Bunk
2006-07-07 7:53 ` Milton Miller
2006-07-07 7:18 ` Adrian Bunk
2006-07-07 7:49 ` Heiko Carstens
2006-07-07 9:33 ` Sam Ravnborg
2006-06-28 16:54 Adrian Bunk
2005-11-07 20:03 Adrian Bunk
2005-11-10 12:28 ` Andrew Morton
2005-11-11 2:12 ` Adrian Bunk
2005-11-11 2:24 ` Andrew Morton
2005-11-11 3:45 ` Randy.Dunlap
2005-11-11 20:18 ` Adrian Bunk
2005-11-11 20:20 ` Adrian Bunk
2005-11-11 20:36 ` Adrian Bunk
2005-11-11 21:24 ` Andrew Morton
2005-11-11 23:34 ` Sam Ravnborg
2005-11-12 0:33 ` Adrian Bunk
2005-08-30 14:54 Adrian Bunk
2005-08-30 16:18 ` Olaf Hering
2005-08-30 16:29 ` Adrian Bunk
2005-08-30 16:38 ` Olaf Hering
2005-08-30 16:48 ` Adrian Bunk
2005-07-30 16:52 Adrian Bunk
2005-07-30 18:08 ` Andrew Morton
2005-07-30 19:44 ` Adrian Bunk
2005-07-30 18:52 ` Sam Ravnborg
2005-07-30 18:59 ` Christoph Hellwig
2005-07-30 19:40 ` Sam Ravnborg
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=20051123155035.2494a746.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
/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®