From: Brian Waite <waite@skycomputers.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] EVB64260 pci scan and cleanup
Date: Wed, 26 Feb 2003 15:33:56 -0500 [thread overview]
Message-ID: <200302261533.56846.waite@skycomputers.com> (raw)
In-Reply-To: <20030226201627.0F250C6E0C@atlas.denx.de>
Ok here are all 3 patches in diff -puRN format
On Wednesday 26 February 2003 3:16 pm, Wolfgang Denk wrote:
> In message <200302261332.50667.waite@skycomputers.com> you wrote:
> > I am attaching 2 seperate patches here. One is specifically for the
> > evb64260 where it could never read properly across P2P bridges.
> > The second does some cleanup to the pci scan code when decending P2P
> > bridges.
> >
> > Please feel free to comment ;)
>
> Can you please re-send all these patches using a proper context diff?
>
> Plain diff output is pretty useless.
>
> See the README for instructions.
>
> Best regards,
>
> Wolfgang Denk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: uboot-ev64260.patch
Type: text/x-diff
Size: 658 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20030226/20beb674/attachment.patch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: uboot-evb64260-pci.patch
Type: text/x-diff
Size: 658 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20030226/20beb674/attachment-0001.patch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: uboot-pciscan.patch
Type: text/x-diff
Size: 1591 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20030226/20beb674/attachment-0002.patch
prev parent reply other threads:[~2003-02-26 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 18:32 [U-Boot-Users] EVB64260 pci scan and cleanup Brian Waite
2003-02-26 18:38 ` [U-Boot-Users] " Brian Waite
2003-02-26 20:16 ` [U-Boot-Users] " Wolfgang Denk
2003-02-26 20:33 ` Brian Waite [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=200302261533.56846.waite@skycomputers.com \
--to=waite@skycomputers.com \
--cc=u-boot@lists.denx.de \
/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