From: Jake Moilanen <moilanen@austin.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH][2/2] RTAS MSI
Date: Mon, 31 Jul 2006 14:55:01 -0500 [thread overview]
Message-ID: <1154375701.29826.389.camel@goblue> (raw)
In-Reply-To: <17613.33279.61050.840408@cargo.ozlabs.ibm.com>
On Mon, 2006-07-31 at 14:07 +1000, Paul Mackerras wrote:
> Jake Moilanen writes:
>
> > -msiobj-y := msi.o msi-apic.o
> > -msiobj-$(CONFIG_IA64_GENERIC) += msi-altix.o
> > -msiobj-$(CONFIG_IA64_SGI_SN2) += msi-altix.o
> > +msiobj-$(CONFIG_X86) += msi.o msi-apic.o
> > +msiobj-$(CONFIG_IA64) += msi.o msi-apic.o
> > +msiobj-$(CONFIG_IA64_GENERIC) += msi.o msi-apic.o msi-altix.o
> > +msiobj-$(CONFIG_IA64_SGI_SN2) += msi.o msi-apic.o msi-altix.o
>
> Doesn't this mean that ia64 configs might now get msi.o and msi-apic.o
> listed twice? Why did you need to change the
> msiobj-$(CONFIG_IA64_GENERIC) and msiobj-$(CONFIG_IA64_SGI_SN2) lines
> at all?
Yup...see the second patch I posted where I fixed up the ia64 configs so
msi.o and msi-apic.o are listed once and msiobj-$(CONFIG_IA64_GENERIC)
and msiobj-$(CONFIG_IA64_SGI_SN2) are not changed.
In a few, I'll be posting another version of the patch which address
Michael's concerns.
next prev parent reply other threads:[~2006-07-31 19:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 18:15 [PATCH][0/2] RTAS MSI Jake Moilanen
2006-07-27 18:17 ` [PATCH][1/2] export msi symbols Jake Moilanen
2006-07-27 18:41 ` Segher Boessenkool
2006-07-27 18:27 ` [PATCH][2/2] RTAS MSI Jake Moilanen
2006-07-27 18:46 ` Segher Boessenkool
2006-07-27 18:50 ` Segher Boessenkool
2006-07-27 19:34 ` Jake Moilanen
2006-07-27 20:35 ` Segher Boessenkool
2006-07-31 4:07 ` Paul Mackerras
2006-07-31 19:55 ` Jake Moilanen [this message]
2006-07-31 4:33 ` Michael Ellerman
2006-07-31 20:47 ` Jake Moilanen
2006-07-31 21:01 ` Jake Moilanen
2006-08-01 23:26 ` Michael Ellerman
2006-08-02 5:35 ` Segher Boessenkool
2006-08-02 9:04 ` Michael Ellerman
2006-08-09 9:50 ` Benjamin Herrenschmidt
2006-08-10 8:03 ` Michael Ellerman
2006-08-10 8:18 ` Benjamin Herrenschmidt
2006-07-28 4:56 ` [PATCH][0/2] " Benjamin Herrenschmidt
2006-07-28 18:43 ` Segher Boessenkool
2006-07-28 18:42 ` Jake Moilanen
2006-07-28 18:53 ` Segher Boessenkool
2006-08-09 2:23 ` Michael Ellerman
2006-08-09 9:52 ` Segher Boessenkool
2006-08-09 10:27 ` Michael Ellerman
2006-08-09 15:41 ` Benjamin Herrenschmidt
2006-08-10 8:22 ` Michael Ellerman
2006-08-10 9:23 ` Benjamin Herrenschmidt
2006-08-09 15:38 ` Benjamin Herrenschmidt
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=1154375701.29826.389.camel@goblue \
--to=moilanen@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--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).