linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 7/7] MPIC MSI backend
Date: Sat, 21 Apr 2007 00:39:55 +1000	[thread overview]
Message-ID: <1177079995.13722.2.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <11965613d9e0cec72d210466d8ec7f6e@kernel.crashing.org>

[-- Attachment #1: Type: text/plain, Size: 661 bytes --]

On Fri, 2007-04-20 at 10:40 +0200, Segher Boessenkool wrote:
> > MPIC MSI backend. Based on code from Segher, heavily hacked by me.
> 
> I guess I'll have to do
> 
> Signed-off-by: Segher Boessenkool <segher@kernel.crashing.org>
> 
> again, you keep losing it :-)

Oh sorry, I do keep losing it. Actually looking at it closer there isn't
any of your code left, except in spirit I guess :)

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: 189 bytes --]

  reply	other threads:[~2007-04-20 14:39 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19  7:35 [PATCH 1/7] Rip out the existing powerpc msi stubs Michael Ellerman
2007-04-19  7:35 ` [PATCH 3/7] RTAS MSI implementation Michael Ellerman
2007-04-19  7:35 ` [PATCH 2/7] Powerpc MSI infrastructure Michael Ellerman
2007-04-21 23:15   ` Milton Miller
2007-04-23  4:28     ` Michael Ellerman
2007-04-19  7:35 ` [PATCH 5/7] Enable MSI mappings for MPIC Michael Ellerman
2007-04-21 23:16   ` Milton Miller
2007-04-22  0:06     ` Benjamin Herrenschmidt
2007-04-22  4:53       ` Milton Miller
2007-04-23  4:10         ` Michael Ellerman
2007-04-19  7:35 ` [PATCH 4/7] Tell Phyp we support MSI Michael Ellerman
2007-04-19  7:35 ` [PATCH 6/7] MPIC MSI allocator Michael Ellerman
2007-04-21 23:17   ` Milton Miller
2007-04-23  4:04     ` Michael Ellerman
2007-04-23  6:20       ` Milton Miller
2007-04-23  3:50   ` Olof Johansson
2007-04-23  3:53     ` Michael Ellerman
2007-04-24  1:29     ` Benjamin Herrenschmidt
2007-04-24  9:26       ` Segher Boessenkool
2007-04-24  9:39         ` Benjamin Herrenschmidt
2007-04-24  9:44           ` Segher Boessenkool
2007-04-24  9:51             ` Benjamin Herrenschmidt
2007-04-19  7:35 ` [PATCH 7/7] MPIC MSI backend Michael Ellerman
2007-04-20  8:40   ` Segher Boessenkool
2007-04-20 14:39     ` Michael Ellerman [this message]
2007-04-21 23:17   ` Milton Miller
2007-04-22  7:06     ` Segher Boessenkool
2007-04-22 19:30       ` Olof Johansson
2007-04-23  4:24         ` Michael Ellerman
2007-04-23  8:24         ` Segher Boessenkool
2007-04-23  8:31           ` Michael Ellerman
2007-04-23 17:33             ` Segher Boessenkool
2007-04-23  3:45     ` Michael Ellerman

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=1177079995.13722.2.camel@concordia.ozlabs.ibm.com \
    --to=michael@ellerman.id.au \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.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).