LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Ed Swarthout <Ed.Swarthout@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Fix mpc8536ds dma interrupt numbers
Date: Mon, 20 Oct 2008 09:46:28 -0500	[thread overview]
Message-ID: <751DF852-228C-49CF-942F-93ABCDE95AE1@kernel.crashing.org> (raw)
In-Reply-To: <1224222092-9301-1-git-send-email-Ed.Swarthout@freescale.com>


On Oct 17, 2008, at 12:41 AM, Ed Swarthout wrote:

> Swap pci1 and pci2 labels -
> Per user manual, pcie1 is at a000 and pcie2 is at 9000.
>
> Signed-off-by: Ed Swarthout <Ed.Swarthout@freescale.com>
> ---
> arch/powerpc/boot/dts/mpc8536ds.dts |   12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)

applied, dropped the pci changes.

- k

      parent reply	other threads:[~2008-10-20 14:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17  5:41 [PATCH] Fix mpc8536ds dma interrupt numbers Ed Swarthout
2008-10-17  6:32 ` Kumar Gala
2008-10-20 14:46 ` 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=751DF852-228C-49CF-942F-93ABCDE95AE1@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=Ed.Swarthout@freescale.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