LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Curtis Wald <CWald@WatchGuardVideo.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] POWERPC 4xx: Fix PCI in AMCC 440EP Yosemite DTS
Date: Mon, 30 Nov 2009 08:41:45 -0500	[thread overview]
Message-ID: <20091130134145.GA2937@zod.rchland.ibm.com> (raw)
In-Reply-To: <13F6A75BE29CE44F801B912901C3EF27022A3993@wgv4.watchguardvideo.local>

On Mon, Nov 16, 2009 at 11:36:40AM -0600, Curtis Wald wrote:
>Yosemite.dts stanza for PCI was copied from Bamboo which has four PCI
>slots; Yosemite only has one PCI slot which is mapped to
>IDSEL 12, ADDR 22, IRQ2 Vector 25, INTA.
>
>Signed-off-by: Curtis Wald <cwald@watchguardvideo.com>

Your patch looks correct (I think), but is very badly word wrapped and
whitespace damaged.  Could you resend?

josh

  reply	other threads:[~2009-11-30 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 17:36 [PATCH] POWERPC 4xx: Fix PCI in AMCC 440EP Yosemite DTS Curtis Wald
2009-11-30 13:41 ` Josh Boyer [this message]
2009-11-30 15:25   ` Curtis Wald
2009-12-04 12:07     ` Josh Boyer
2009-12-04 14:19       ` Curtis Wald

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=20091130134145.GA2937@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=CWald@WatchGuardVideo.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