From: Greg KH <gregkh@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
maule@sgi.com
Subject: Re: [PATCH] (-mm) drivers/pci/msi: explicit declaration of msi_register
Date: Tue, 14 Mar 2006 13:59:22 -0800 [thread overview]
Message-ID: <20060314215922.GA12257@suse.de> (raw)
In-Reply-To: <20060314134535.72eb7243.akpm@osdl.org>
On Tue, Mar 14, 2006 at 01:45:35PM -0800, Andrew Morton wrote:
> "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com> wrote:
> >
> > Declare msi_register() in msi.h.
> >
> > The patch is especially necessary for ia64 on which most of files
> > emit compiler warnings like below:
> > 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,
>
> I wonder why I didn't get that. Need a better ia64 config I guess.
>
> > Signed-off-by: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
> >
> > --- linux-2.6.16-rc6-mm1.orig/include/asm-ia64/msi.h 2006-03-14 13:54:11.000000000 -0500
> > +++ linux-2.6.16-rc6-mm1/include/asm-ia64/msi.h 2006-03-14 14:05:26.000000000 -0500
> > @@ -15,6 +15,7 @@ static inline void set_intr_gate (int nr
> > #define MSI_TARGET_CPU_SHIFT 4
> >
> > extern struct msi_ops msi_apic_ops;
> > +extern int msi_register(struct msi_ops *);
> >
> > /* default ia64 msi init routine */
> > static inline int ia64_msi_init(void)
>
> The offending patch is gregkh-pci-msi-vector-targeting-abstractions.patch.
>
> That patch already adds a declaration for msi_register(), in
> drivers/pci/pci.h. We don't want to add a duplicated declaration like
> this.
>
> One option might be to create inclued/linux/msi.h, put this declaration in
> there then include <asm/msi.h>. Possibly some other declarations should be
> moved into linux/msi.h as well.
Ugh. What is the file that is causing the problem? What is "include2"
in your directory path above?
Whatever .c file has it, should just include the internal pci.h file
that already has this prototype, like Andrew says...
thanks,
greg k-h
next prev parent reply other threads:[~2006-03-14 21:59 UTC|newest]
Thread overview: 23+ 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:45 ` Andrew Morton
2006-03-14 21:59 ` Greg KH [this message]
2006-03-14 22:25 ` Matthew Wilcox
2006-03-15 0:51 ` Jun'ichi Nomura
2006-03-15 23:55 ` Greg KH
2006-03-16 15:19 ` Jun'ichi Nomura
2006-03-16 18:19 ` Mark Maule
2006-03-16 19:32 ` Jun'ichi Nomura
2006-03-16 19:41 ` Mark Maule
2006-03-16 23:28 ` Greg KH
2006-03-16 23:37 ` Roland Dreier
2006-03-16 23:45 ` Grant Grundler
2006-03-16 23:47 ` Greg KH
2006-03-16 23:41 ` Grant Grundler
2006-03-16 23:49 ` Greg KH
2006-03-17 0:41 ` Grant Grundler
2006-03-17 1:18 ` Mark Maule
2006-03-16 15:29 ` Jun'ichi Nomura
2006-03-14 21:57 ` Adrian Bunk
2006-03-14 23:55 ` Jun'ichi Nomura
2006-03-15 0:09 ` Mark Maule
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=20060314215922.GA12257@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox