From: Kumar Gala <galak@kernel.crashing.org>
To: Jeremy McNicoll <jeremy.mcnicoll@windriver.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] sbc8548: fix incorrect PCI-X and PCI interrupt map
Date: Fri, 7 Mar 2008 16:51:46 -0600 [thread overview]
Message-ID: <5F3A8414-A136-4C96-A419-1E0CCBDFABDC@kernel.crashing.org> (raw)
In-Reply-To: <1204920849-31741-1-git-send-email-jeremy.mcnicoll@windriver.com>
On Mar 7, 2008, at 2:14 PM, Jeremy McNicoll wrote:
> The following patch allows interrupts to occur on the
> sbc8548. Currently PCI and PCI-X devices get assigned an IRQ
> but the interrupt count never increases. This solves the
> problem and adds PCI support as well.
>
> Signed-off-by: Jeremy McNicoll <jeremy.mcnicoll@windriver.com>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> ---
> arch/powerpc/boot/dts/sbc8548.dts | 16 +++++++++++-----
> 1 files changed, 11 insertions(+), 5 deletions(-)
applied.
- k
prev parent reply other threads:[~2008-03-07 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 20:14 [PATCH] sbc8548: fix incorrect PCI-X and PCI interrupt map Jeremy McNicoll
2008-03-07 22:51 ` Kumar Gala [this message]
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=5F3A8414-A136-4C96-A419-1E0CCBDFABDC@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=jeremy.mcnicoll@windriver.com \
--cc=linuxppc-dev@ozlabs.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