From: Michael Ellerman <michael@ellerman.id.au>
To: Joe Perches <joe@perches.com>
Cc: Nishanth Aravamudan <nacc@us.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Florian Mickler <florian@mickler.org>
Subject: Re: [PATCH] powerpc: disable MSI using new interface if possible
Date: Thu, 10 Mar 2011 14:35:21 +1100 [thread overview]
Message-ID: <1299728121.6272.46.camel@concordia> (raw)
In-Reply-To: <1299716903.20104.134.camel@Joe-Laptop>
[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]
On Wed, 2011-03-09 at 16:28 -0800, Joe Perches wrote:
> On Thu, 2011-03-10 at 10:12 +1100, Michael Ellerman wrote:
> > True my last patch may have been two years ago, but I _wrote the entire
> > file_, and essentially no one else has ever touched it.
> >
> > > $ ./scripts/get_maintainer.pl -f arch/powerpc/platforms/pseries/msi.c
> > > Benjamin Herrenschmidt <benh@kernel.crashing.org> (supporter:LINUX FOR POWERPC...)
> > > Paul Mackerras <paulus@samba.org> (supporter:LINUX FOR POWERPC...)
> > > Grant Likely <grant.likely@secretlab.ca> (maintainer:OPEN FIRMWARE AND...)
> > > linuxppc-dev@lists.ozlabs.org (open list:LINUX FOR POWERPC...)
> > > linux-kernel@vger.kernel.org (open list)
> > > devicetree-discuss@lists.ozlabs.org (open list:OPEN FIRMWARE AND...)
> > >
> > > If you don't like how it currently works, suggest
> > > improvements.
> >
> > I think I was suggesting that I should be in that list :)
>
> $ ./scripts/get_maintainer.pl -f --git-blame arch/powerpc/platforms/pseries/msi.c
> Benjamin Herrenschmidt <benh@kernel.crashing.org> (supporter:LINUX FOR POWERPC...,commits:8/11=73%)
> Paul Mackerras <paulus@samba.org> (supporter:LINUX FOR POWERPC...,commits:4/11=36%)
> Grant Likely <grant.likely@secretlab.ca> (maintainer:OPEN FIRMWARE AND...)
> Michael Ellerman <michael@ellerman.id.au> (authored lines:481/481=100%,commits:11/11=100%)
> Linas Vepstas <linas@austin.ibm.com> (commits:1/11=9%)
> linuxppc-dev@lists.ozlabs.org (open list:LINUX FOR POWERPC...)
> linux-kernel@vger.kernel.org (open list)
> devicetree-discuss@lists.ozlabs.org (open list:OPEN FIRMWARE AND...)
That's awesome. But it's not the default, so hardly anyone will ever use
it :)
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-10 3:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 19:39 [PATCH 1/2] powerpc: disable MSI using new interface if possible Nishanth Aravamudan
2011-03-03 19:39 ` [PATCH 2/2] powerpc/msi: clarify call to check_req_msi{,x} Nishanth Aravamudan
2011-03-03 19:44 ` [PATCH 1/2] powerpc: disable MSI using new interface if possible Nishanth Aravamudan
2011-03-04 1:05 ` Michael Ellerman
2011-03-04 1:41 ` [PATCH] " Nishanth Aravamudan
2011-03-04 3:01 ` Michael Ellerman
2011-03-04 7:24 ` Nishanth Aravamudan
2011-03-08 5:34 ` Nishanth Aravamudan
2011-03-09 22:54 ` Michael Ellerman
2011-03-04 3:06 ` Michael Ellerman
2011-03-04 3:29 ` Joe Perches
2011-03-04 11:13 ` Florian Mickler
2011-03-09 23:12 ` Michael Ellerman
2011-03-10 0:28 ` Joe Perches
2011-03-10 0:46 ` Nishanth Aravamudan
2011-03-10 3:35 ` Michael Ellerman [this message]
2011-03-10 3:45 ` Joe Perches
2011-03-10 7:04 ` Florian Mickler
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=1299728121.6272.46.camel@concordia \
--to=michael@ellerman.id.au \
--cc=florian@mickler.org \
--cc=joe@perches.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nacc@us.ibm.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;
as well as URLs for NNTP newsgroup(s).