From: Greg KH <greg@kroah.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Olof Johannsson <olof@lixom.net>,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 2/7] Powerpc MSI implementation
Date: Sat, 13 Jan 2007 11:27:34 -0800 [thread overview]
Message-ID: <20070113192734.GA30867@kroah.com> (raw)
In-Reply-To: <1168667863.5011.44.camel@localhost.localdomain>
On Sat, Jan 13, 2007 at 04:57:43PM +1100, Benjamin Herrenschmidt wrote:
>
> > No, what's wrong with just fixing everything up to work properly all at
> > once? The Altix code should have been a step forward in making this
> > "abstracted" into something that other arches could use. If that's not
> > true, then please work everything so that it all works nicely together.
> >
> > In short, I don't want to see two different implementations in the tree
> > at the same time, that's not acceptable, sorry.
>
> So you are saying that despite the current stuff being beyond repair, we
> can't provide an alternate working implementation that fits our needs
> unless we also port over Altic and Intel, which we don't know and don't
> have testing gear, not even within our arch code ?
I'm saying I don't want to see 2 different MSI implementations in the
kernel. I'm sure you can understand this reasoning.
I misunderstood your original patches in that I thought you were
cleaning up the generic versions for everyone, not creating a separate
set of APIs. Sorry for the misunderstanding.
thanks,
greg k-h
next prev parent reply other threads:[~2007-01-13 19:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 11:25 [PATCH 0/7] Powerpc MSI Implementation Michael Ellerman
2007-01-11 11:25 ` [PATCH 1/7] Rip out the existing powerpc msi stubs Michael Ellerman
2007-01-11 21:31 ` Christoph Hellwig
2007-01-11 11:25 ` [PATCH 2/7] Powerpc MSI implementation Michael Ellerman
2007-01-11 19:44 ` Greg KH
2007-01-11 21:20 ` Benjamin Herrenschmidt
2007-01-11 21:54 ` Benjamin Herrenschmidt
2007-01-12 23:13 ` Greg KH
2007-01-13 5:57 ` Benjamin Herrenschmidt
2007-01-13 19:27 ` Greg KH [this message]
2007-01-13 20:40 ` Benjamin Herrenschmidt
2007-01-12 23:11 ` Greg KH
2007-01-11 21:36 ` Christoph Hellwig
2007-01-12 7:27 ` Benjamin Herrenschmidt
2007-01-11 11:25 ` [PATCH 3/7] Enable MSI on Powerpc Michael Ellerman
2007-01-11 21:37 ` Christoph Hellwig
2007-01-12 7:24 ` Benjamin Herrenschmidt
2007-01-11 11:25 ` [PATCH 5/7] MPIC MSI backend Michael Ellerman
2007-01-11 11:25 ` [PATCH 4/7] MPIC MSI allocator Michael Ellerman
2007-01-11 15:14 ` Segher Boessenkool
2007-01-11 17:19 ` Will Schmidt
2007-01-11 17:27 ` Segher Boessenkool
2007-01-12 0:27 ` Olof Johansson
2007-01-12 0:33 ` Michael Ellerman
2007-01-11 11:25 ` [PATCH 6/7] Enable MSI mappings for MPIC Michael Ellerman
2007-01-11 15:22 ` Segher Boessenkool
2007-01-11 11:25 ` [PATCH 7/7] Activate MSI for the MPIC backend on U3 Michael Ellerman
2007-01-11 15:23 ` [PATCH 0/7] Powerpc MSI Implementation Segher Boessenkool
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=20070113192734.GA30867@kroah.com \
--to=greg@kroah.com \
--cc=benh@kernel.crashing.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--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).