public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: kai@germaschewski.name, sam@ravnborg.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] add -Werror-implicit-function-declaration to CFLAGS
Date: Thu, 6 Jul 2006 14:20:41 -0400	[thread overview]
Message-ID: <20060706182041.GF13168@redhat.com> (raw)
In-Reply-To: <20060706163728.GN26941@stusta.de>

On Thu, Jul 06, 2006 at 06:37:28PM +0200, Adrian Bunk wrote:
 > Currently, using an undeclared function gives a compile warning, but it 
 > can lead to a nasty to debug runtime stack corruptions 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.
 > 
 > Signed-off-by: Adrian Bunk <bunk@stusta.de>

I've been carrying pretty much the same patch in Fedora for months,
and making sure it still builds across x86/x86-64/s390/ia64/ppc32/ppc64.
It saves a lot of time when you're building a large heavily modular kernel.
(like that from a distro config say)

Signed-off-by: Dave Jones <davej@redhat.com>

-- 
http://www.codemonkey.org.uk

  parent reply	other threads:[~2006-07-06 18:22 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 16:37 [2.6 patch] add -Werror-implicit-function-declaration to CFLAGS Adrian Bunk
2006-07-06 18:05 ` Jesper Juhl
2006-07-06 18:20 ` Dave Jones [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2006-07-07 17:10 Luck, Tony
2006-06-28 16:54 Adrian Bunk
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
2005-11-24  0:13       ` 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=20060706182041.GF13168@redhat.com \
    --to=davej@redhat.com \
    --cc=bunk@stusta.de \
    --cc=kai@germaschewski.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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