From: Zang Roy-r61911 <tie-fei.zang@freescale.com>
To: Jon Loeliger <jdl@freescale.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 1/3] Let subordinate transparent bridges be transparent.
Date: 31 May 2007 14:53:15 +0800 [thread overview]
Message-ID: <1180594395.16792.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1180462974.13106.61.camel@ld0161-tx32>
On Wed, 2007-05-30 at 02:22, Jon Loeliger wrote:
> From: York Sun <yorksun@freescale.com>
>
> In pcibios_fixup_bus(), bridges that are subordinate
> to transparent bridges were still relocating their
> IORESOURCE_IO start and end values.
>
> Fix this by preventing the transparent bridge from
> relocating the start and end values, thus allowing the
> subordinate non-transparent bridge full molestation rights.
>
> Signed-off-by: York Sun <yorksun@freescale.com>
> Signed-off-by: Andy Fleming <afleming@freescale.com>
> Signed-off-by: Jon Loeliger <jdl@freescale.com>
> ---
Acked-by: Roy Zang <tie-fei.zang@freescale.com>
prev parent reply other threads:[~2007-05-31 6:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 18:22 [PATCH 1/3] Let subordinate transparent bridges be transparent Jon Loeliger
2007-05-31 6:53 ` Zang Roy-r61911 [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=1180594395.16792.2.camel@localhost.localdomain \
--to=tie-fei.zang@freescale.com \
--cc=jdl@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;
as well as URLs for NNTP newsgroup(s).