public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@pathscale.com>
To: akpm@osdl.org, greg@kroah.com, rdreier@cisco.com,
	linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: [PATCH 0 of 18] ipath driver - for inclusion in 2.6.17
Date: Thu, 23 Mar 2006 20:41:32 -0800	[thread overview]
Message-ID: <patchbomb.1143175292@eng-12.pathscale.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

Hi -

This is a submission of the ipath driver for inclusion in 2.6.17.
Andrew, if this looks good to you, please apply.

We have addressed all earlier rounds of feedback; the driver is stable;
it compiles with no compiler or sparse warnings against current -git (it's
comprehensively annotated for sparse); and I think it's in good shape.
We have gone to great lengths over the past several months to make it
an exemplary kernel citizen.

Changes since the last round of review comments:

  - We have rewritten some code in ipath_rc.c to make it more
    comprehensible and maintainable.

  - The ipathfs filesystem now handles hotplugged devices.

  - Miscellaneous fixes requested by Greg and Andrew.

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.

	<b

             reply	other threads:[~2006-03-24  4:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24  4:41 Bryan O'Sullivan [this message]
2006-03-24  4:41 ` [PATCH 1 of 18] ipath - core device driver Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 2 of 18] ipath - core driver header files Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 3 of 18] ipath - copy and send routines for sending an skb Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 4 of 18] ipath - support for HyperTransport devices Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 5 of 18] ipath - support for PCI Express devices Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 6 of 18] ipath - chip initialisation code Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 7 of 18] ipath - misc driver support code Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 8 of 18] ipath - sysfs and ipathfs support for core driver Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 9 of 18] ipath - char devices for diagnostics and lightweight subnet management Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 10 of 18] ipath - support for userspace apps using core driver Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 11 of 18] ipath - layering interfaces used by higher-level driver code Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 12 of 18] ipath - infiniband header files Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 13 of 18] ipath - infiniband UC and UD protocol support Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 14 of 18] ipath - infiniband RC " Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 15 of 18] ipath - misc infiniband code, part 1 Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 16 of 18] ipath - misc infiniband code, part 2 Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 17 of 18] ipath - infiniband verbs support Bryan O'Sullivan
2006-03-24  4:41 ` [PATCH 18 of 18] ipath - kbuild infrastructure Bryan O'Sullivan
2006-03-24 18:57 ` [PATCH 0 of 18] ipath driver - for inclusion in 2.6.17 Roland Dreier
2006-03-24 19:11   ` Bryan O'Sullivan
2006-03-24 20:57     ` Muli Ben-Yehuda
2006-03-24 21:19     ` [openib-general] " Roland Dreier
2006-03-24 22:33       ` Bryan O'Sullivan
2006-03-24 23:21         ` Roland Dreier
2006-03-25  0:03           ` 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.1143175292@eng-12.pathscale.com \
    --to=bos@pathscale.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.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