From: Jon Loeliger <jdl@freescale.com>
To: Roy Zang <tie-fei.zang@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: RE: [PATCH 3/3] Modified quirk_mpc8641_transparent() to initializebridge resources.
Date: Thu, 31 May 2007 09:10:13 -0500 [thread overview]
Message-ID: <1180620613.1965.16.camel@ld0161-tx32> (raw)
In-Reply-To: <7EA18FDD2DC2154AA3BD6D2F22A62A0E7EDA24@zch01exm23.fsl.freescale.net>
On Thu, 2007-05-31 at 01:48, Zang Roy-r61911 wrote:
> > Can this be merged with Zhang's "Set RC of mpc8641 to transparent
> > bridge for transfer legacy I/O access." patch since it pretty much
> > supersedes it.
>
> I should be!
> But why apply them sperately?
> They refect differnet content and stage. For end user, they will only
> see the unified code :-).
> Roy
I have respun these two PCI-E patch sets into one and will post
them again.
jdl
prev parent reply other threads:[~2007-05-31 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 18:23 [PATCH 3/3] Modified quirk_mpc8641_transparent() to initialize bridge resources Jon Loeliger
2007-05-29 20:49 ` Kumar Gala
2007-05-31 6:48 ` [PATCH 3/3] Modified quirk_mpc8641_transparent() to initializebridge resources Zang Roy-r61911
2007-05-31 12:33 ` Kumar Gala
2007-05-31 14:10 ` Jon Loeliger [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=1180620613.1965.16.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=tie-fei.zang@freescale.com \
/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).