From: colin.tuckley@arm.com (Colin Tuckley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] Add PCI support for ARM RealView boards
Date: Wed, 22 Dec 2010 14:09:25 -0000 [thread overview]
Message-ID: <000501cba1e1$d739bcf0$85ad36d0$@tuckley@arm.com> (raw)
Apologies for the empty header email for this series it should have said:
The following series implements the PCI support for the
ARM RealView NEC custom Northbridge based reference boards
(PBA8, PB11MPCore and PBX).
The boards have a PCIX root complex connected to PCI and
PCIe bridges. Each board has 2 PCI slots and 2 PCIe slots.
This is the second pass of posting these patches to the list - all previous
comments have been addressed.
Colin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20101222/f1271460/attachment.html>
next reply other threads:[~2010-12-22 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 14:09 Colin Tuckley [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-20 13:02 [PATCH 0/6] Add PCI support for ARM RealView boards Colin Tuckley
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='000501cba1e1$d739bcf0$85ad36d0$@tuckley@arm.com' \
--to=colin.tuckley@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).