From: "Bryan O'Sullivan" <bos@pathscale.com>
To: rdreier@cisco.com
Cc: linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: [PATCH 0 of 16] ipath - driver submission for 2.6.17
Date: Wed, 29 Mar 2006 15:23:23 -0800 [thread overview]
Message-ID: <patchbomb.1143674603@chalcedony.internal.keyresearch.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
This is a submission of the ipath driver for inclusion in 2.6.17.
Roland, if this looks good to you, please apply.
Changes since the last round of review comments from Roland:
- Support for PathScale userland SMA dropped
- Passes sparse with CF=-D__CHECK_ENDIAN__
- Builds cleanly on ia64
- A few other little fixes here and there
If you have any comments or suggestions, please let me know.
The ipath driver is a driver for PathScale InfiniPath host channel
adapters (HCAs) based on the HT-400 and PE-800 chips, including the
InfiniPath HT-460, the small form factor InfiniPath HT-460, the InfiniPath
HT-470 and the Linux Networx LS/X.
The core driver manages the hardware, and provides a fast memory-mapped
interface to the hardware for userspace networking applications.
Our implementation of the Infiniband protocols and integration into the
kernel's Infiniband stack is written as a layer on top of the core driver.
next reply other threads:[~2006-03-29 23:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 23:23 Bryan O'Sullivan [this message]
2006-03-29 23:23 ` [PATCH 1 of 16] ipath - core device driver Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 2 of 16] ipath - core driver header files Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 3 of 16] ipath - support for HyperTransport devices Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 4 of 16] ipath - support for PCI Express devices Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 5 of 16] ipath - chip initialisation code, and diag support Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 6 of 16] ipath - misc driver support code Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 7 of 16] ipath - sysfs and ipathfs support for core driver Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 8 of 16] ipath - support for userspace apps using " Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 9 of 16] ipath - layering interfaces used by higher-level driver code Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 10 of 16] ipath - infiniband header files Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 11 of 16] ipath - infiniband UC and UD protocol support Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 12 of 16] ipath - infiniband RC " Bryan O'Sullivan
2006-03-30 20:36 ` Pavel Machek
2006-03-29 23:23 ` [PATCH 13 of 16] ipath - misc infiniband code, part 1 Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 14 of 16] ipath - misc infiniband code, part 2 Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 15 of 16] ipath - infiniband verbs support Bryan O'Sullivan
2006-03-29 23:23 ` [PATCH 16 of 16] ipath - kbuild infrastructure Bryan O'Sullivan
2006-03-30 21:06 ` Roland Dreier
2006-03-30 21:55 ` Bryan O'Sullivan
2006-03-30 22:36 ` Roland Dreier
2006-03-31 3:53 ` Sam Ravnborg
2006-03-30 20:59 ` [PATCH 0 of 16] ipath - driver submission for 2.6.17 Roland Dreier
2006-03-30 21:54 ` Bryan O'Sullivan
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=patchbomb.1143674603@chalcedony.internal.keyresearch.com \
--to=bos@pathscale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.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