From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jake Moilanen <moilanen@austin.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH][2/2] RTAS MSI
Date: Thu, 27 Jul 2006 22:35:43 +0200 [thread overview]
Message-ID: <56C6BA2D-C235-4DD3-BEEA-5E253DF77A8D@kernel.crashing.org> (raw)
In-Reply-To: <1154028871.29826.261.camel@goblue>
>> These two lines don't need the msi.o and msi-altix.o AFAICS.
>
> Yup, you are right...updated patch included below.
Looks fine now, thanks.
>>> +msiobj-$(CONFIG_PPC_PSERIES) += msi-rtas.o
>>
>> I think this file should live in arch/powerpc, and so should this
>> Makefile fragment.
>
> I'm following the current MSI methodologies where arch specific MSI
> code
> lives in drivers/pci. This is just like msi-altix.c.
True, but our core support lives in arch/. The same is true for PHB
code etc.; if Altix messed this up, that doesn't mean we need to :-)
>> Other than that, can we please have the part that doesn't build the
>> "generic" MSI stuff included ASAP?
This would naturally fall out as a separate patch then, as well.
>>> Index: 2.6-msi/drivers/pci/msi-rtas.c
>>
>> Maybe msi-papr.c is a better name btw? Not that I care :-)
>
> IMHO I don't like PAPR names because they like changing them on a
> whim.
> RTAS is a bit more persistent.
Maybe msi-pseries then? Oh wait, they changed that name too ;-)
> I don't really care...If anyone feels real strongly about it, I'll
> change it.
If you move this code to arch/powerpc/platforms/pseries/, you could
just call it "msi.c". I don't like the msi-rtas name -- but, I don't
feel that strongly about it, just a suggestion.
Segher
next prev parent reply other threads:[~2006-07-27 20:35 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 [this message]
2006-07-31 4:07 ` Paul Mackerras
2006-07-31 19:55 ` Jake Moilanen
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=56C6BA2D-C235-4DD3-BEEA-5E253DF77A8D@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--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).