From: Roland Dreier <rolandd@cisco.com>
To: "Ruslan V. Sushko" <rsushko@ru.mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH 2/3] ppc32: PCIX support for Yucca board
Date: Wed, 30 Nov 2005 10:11:33 -0800 [thread overview]
Message-ID: <52r78yqa3u.fsf@cisco.com> (raw)
In-Reply-To: <1132763369.31328.22.camel@mephisto.spb.rtsoft.ru> (Ruslan V. Sushko's message of "Wed, 23 Nov 2005 19:29:29 +0300")
Again, looks pretty good, but I would like to see the whitespace fixes
separated from adding PCI-X support.
- R.
next prev parent reply other threads:[~2005-11-30 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 14:25 [PATCH 1/3] ppc32: Fix a few issues in Yucca PCIe functionality Ruslan V. Sushko
2005-11-21 17:47 ` Dale Farnsworth
2005-11-23 16:29 ` Ruslan V. Sushko
2005-11-30 18:09 ` Roland Dreier
2005-11-23 16:29 ` [PATCH 2/3] ppc32: PCIX support for Yucca board Ruslan V. Sushko
2005-11-30 18:11 ` Roland Dreier [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-21 14:26 Ruslan V. Sushko
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=52r78yqa3u.fsf@cisco.com \
--to=rolandd@cisco.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rsushko@ru.mvista.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).