From: Johannes Thumshirn <johannes.thumshirn@men.de>
To: Scott Wood <scottwood@freescale.com>
Cc: Johannes Thumshirn <johannes.thumshirn@men.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linuxppc-dev@lists.ozlabs.org,
'David Engster' <david.engster@mahr.de>
Subject: Re: FSL MSI Mapping
Date: Wed, 29 Oct 2014 07:54:51 +0100 [thread overview]
Message-ID: <20141029065451.GA2441@jtlinux> (raw)
In-Reply-To: <1414523418.23458.98.camel@snotra.buserror.net>
On Tue, Oct 28, 2014 at 02:10:18PM -0500, Scott Wood wrote:
> On Tue, 2014-10-28 at 18:06 +0100, Johannes Thumshirn wrote:
> > Hi,
> >
> > I got notified about your patch to support multiple MSI Vectors on Freescale
> > PowerPC platforms. Is there any reason why it wasn't applied until now? I
> > couldn't find anything about it in the list archives.
> >
> > I think it would be a real benefit for all to have multiple MSI vecotrs on
> > PowerPCs.
>
> Could you provide a patchwork link to the patch you're talking about?
Unfortunately I couldn't find it in the ppc patchwork, but here are the links to
the patch series in the list archives:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-February/115484.html
https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-February/115485.html
https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-February/115486.html
Thanks,
Johannes
next prev parent reply other threads:[~2014-10-29 7:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 17:06 FSL MSI Mapping Johannes Thumshirn
2014-10-28 19:10 ` Scott Wood
2014-10-29 6:54 ` Johannes Thumshirn [this message]
2014-11-03 21:57 ` Scott Wood
2014-10-30 3:51 ` Michael Ellerman
2014-10-30 6:58 ` Johannes Thumshirn
2014-10-31 8:12 ` Johannes Thumshirn
2014-10-31 11:28 ` Sebastian Andrzej Siewior
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=20141029065451.GA2441@jtlinux \
--to=johannes.thumshirn@men.de \
--cc=bigeasy@linutronix.de \
--cc=david.engster@mahr.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.