All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	Greg KH <gregkh@suse.de>,
	maule@sgi.com, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] (-mm) drivers/pci/msi: explicit declaration of msi_register
Date: Tue, 14 Mar 2006 21:57:36 +0000	[thread overview]
Message-ID: <20060314215736.GV13973@stusta.de> (raw)
In-Reply-To: <44172F0E.6070708@ce.jp.nec.com>

On Tue, Mar 14, 2006 at 04:01:02PM -0500, Jun'ichi Nomura wrote:
> Hello,
> 
> In 2.6.16-rc6-mm1, I've seen tons of compiler warnings on ia64:
> 
> include2/asm/msi.h: In function `ia64_msi_init':
> include2/asm/msi.h:23: warning: implicit declaration of function `msi_register'
> In file included from include2/asm/machvec.h:408,
>                  from include2/asm/io.h:70,
>                  from include2/asm/smp.h:20,
>                  from /build/rc6/source/include/linux/smp.h:22,
> 
> The problem is that msi_register() is used in ia64_msi_init()
> without declaration.
> Since ia64_msi_init() is a part of machine vector, most of files
> hit this warning and may hide other important messages.
>...

To avoid any wrong impression:

This kind of warnings isn't harmless.

gcc tries to guess the prototype of the function, and if gcc guessed 
wrong this can cause nasty and hard to debug runtime errors.

> Thanks,
>...

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


WARNING: multiple messages have this Message-ID (diff)
From: Adrian Bunk <bunk@stusta.de>
To: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	Greg KH <gregkh@suse.de>,
	maule@sgi.com, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] (-mm) drivers/pci/msi: explicit declaration of msi_register
Date: Tue, 14 Mar 2006 22:57:36 +0100	[thread overview]
Message-ID: <20060314215736.GV13973@stusta.de> (raw)
In-Reply-To: <44172F0E.6070708@ce.jp.nec.com>

On Tue, Mar 14, 2006 at 04:01:02PM -0500, Jun'ichi Nomura wrote:
> Hello,
> 
> In 2.6.16-rc6-mm1, I've seen tons of compiler warnings on ia64:
> 
> include2/asm/msi.h: In function `ia64_msi_init':
> include2/asm/msi.h:23: warning: implicit declaration of function `msi_register'
> In file included from include2/asm/machvec.h:408,
>                  from include2/asm/io.h:70,
>                  from include2/asm/smp.h:20,
>                  from /build/rc6/source/include/linux/smp.h:22,
> 
> The problem is that msi_register() is used in ia64_msi_init()
> without declaration.
> Since ia64_msi_init() is a part of machine vector, most of files
> hit this warning and may hide other important messages.
>...

To avoid any wrong impression:

This kind of warnings isn't harmless.

gcc tries to guess the prototype of the function, and if gcc guessed 
wrong this can cause nasty and hard to debug runtime errors.

> Thanks,
>...

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2006-03-14 21:57 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14 21:01 [PATCH] (-mm) drivers/pci/msi: explicit declaration of msi_register Jun'ichi Nomura
2006-03-14 21:01 ` Jun'ichi Nomura
2006-03-14 21:45 ` [PATCH] (-mm) drivers/pci/msi: explicit declaration of Andrew Morton
2006-03-14 21:45   ` [PATCH] (-mm) drivers/pci/msi: explicit declaration of msi_register Andrew Morton
2006-03-14 21:59   ` Greg KH
2006-03-14 21:59     ` Greg KH
2006-03-14 22:25     ` Matthew Wilcox
2006-03-14 22:25       ` Matthew Wilcox
2006-03-15  0:51   ` Jun'ichi Nomura
2006-03-15  0:51     ` Jun'ichi Nomura
2006-03-15 23:55     ` Greg KH
2006-03-15 23:55       ` Greg KH
2006-03-16 15:19       ` Jun'ichi Nomura
2006-03-16 15:19         ` Jun'ichi Nomura
2006-03-16 18:19         ` Mark Maule
2006-03-16 18:19           ` Mark Maule
2006-03-16 19:32           ` Jun'ichi Nomura
2006-03-16 19:32             ` Jun'ichi Nomura
2006-03-16 19:41             ` Mark Maule
2006-03-16 19:41               ` Mark Maule
2006-03-16 23:28               ` Greg KH
2006-03-16 23:28                 ` Greg KH
2006-03-16 23:37                 ` Roland Dreier
2006-03-16 23:37                   ` Roland Dreier
2006-03-16 23:45                   ` Grant Grundler
2006-03-16 23:45                     ` Grant Grundler
2006-03-16 23:47                   ` Greg KH
2006-03-16 23:47                     ` Greg KH
2006-03-16 23:41           ` Grant Grundler
2006-03-16 23:41             ` Grant Grundler
2006-03-16 23:49             ` Greg KH
2006-03-16 23:49               ` Greg KH
2006-03-17  0:41               ` Grant Grundler
2006-03-17  0:41                 ` Grant Grundler
2006-03-17  1:18                 ` Mark Maule
2006-03-17  1:18                   ` Mark Maule
2006-03-16 15:29       ` Jun'ichi Nomura
2006-03-16 15:29         ` Jun'ichi Nomura
2006-03-14 21:57 ` Adrian Bunk [this message]
2006-03-14 21:57   ` Adrian Bunk
2006-03-14 23:55   ` Jun'ichi Nomura
2006-03-14 23:55     ` Jun'ichi Nomura
2006-03-15  0:09     ` Mark Maule
2006-03-15  0:09       ` Mark Maule
2006-03-15  1:04       ` Jun'ichi Nomura
2006-03-15  1:04         ` Jun'ichi Nomura

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=20060314215736.GV13973@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=j-nomura@ce.jp.nec.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maule@sgi.com \
    /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.