From: Michael Ellerman <michael@ellerman.id.au>
To: Jake Moilanen <moilanen@austin.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [RFC/PATCH 4/4] Enable MSI on Powerpc
Date: Thu, 28 Sep 2006 16:07:20 +1000 [thread overview]
Message-ID: <1159423641.12398.14.camel@localhost.localdomain> (raw)
In-Reply-To: <1159386365.5542.115.camel@goblue>
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
On Wed, 2006-09-27 at 14:46 -0500, Jake Moilanen wrote:
> On Fri, 2006-08-18 at 18:13 +1000, Michael Ellerman wrote:
> > Allow PCI_MSI to build on POWERPC.
> >
> > Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> > ---
> >
> > drivers/pci/Kconfig | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Index: git/drivers/pci/Kconfig
> > ===================================================================
> > --- git.orig/drivers/pci/Kconfig
> > +++ git/drivers/pci/Kconfig
> > @@ -4,7 +4,7 @@
> > config PCI_MSI
> > bool "Message Signaled Interrupts (MSI and MSI-X)"
> > depends on PCI
> > - depends on (X86_LOCAL_APIC && X86_IO_APIC) || IA64
> > + depends on (X86_LOCAL_APIC && X86_IO_APIC) || IA64 || POWERPC
>
> Shouldn't this be PPC?
Maybe. If we use PPC then MSI will get built for arch/ppc as well which
won't work - so I think we should have a POWERPC symbol, I sent that as
a separate patch a while back but it seems to have hit the floor.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
prev parent reply other threads:[~2006-09-28 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 8:13 [RFC/PATCH 4/4] Enable MSI on Powerpc Michael Ellerman
2006-09-27 19:46 ` Jake Moilanen
2006-09-28 6:07 ` Michael Ellerman [this message]
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=1159423641.12398.14.camel@localhost.localdomain \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=moilanen@austin.ibm.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).