All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Steve Wise <swise@opengridcomputing.com>
Cc: openib-general@openib.org, netdev@vger.kernel.org
Subject: Re: [PATCH v4 7/7] AMSO1100 Makefiles and Kconfig changes.
Date: Mon, 28 Aug 2006 16:07:15 -0700	[thread overview]
Message-ID: <adazmdoo3x8.fsf@cisco.com> (raw)
In-Reply-To: <20060803210738.16572.74032.stgit@dell3.ogc.int> (Steve Wise's message of "Thu, 03 Aug 2006 16:07:38 -0500")

I'm finally getting around to merging this up, and:

 > --- /dev/null
 > +++ b/drivers/infiniband/hw/amso1100/README
 > @@ -0,0 +1,11 @@
 > +This is the OpenFabrics provider driver for the 
 > +AMSO1100 1Gb RNIC adapter. 
 > +
 > +This adapter is available in limited quantities 
 > +for development purposes from Open Grid Computing.
 > +
 > +This driver requires the IWCM and CMA mods necessary
 > +to support iWARP.
 > +
 > +Contact tom@opengridcomputing.com for more information.
 > +

I don't think this belongs in the drivers directory.  In fact, is it
worth having this in the kernel at all?

How about if I just add a MAINTAINERS entry for amso1100 pointing at
tom@opengridcomputing.com ?

 - R.

  reply	other threads:[~2006-08-28 23:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 21:07 [PATCH v4 0/7] Ammasso 1100 iWARP Driver Steve Wise
2006-08-03 21:07 ` [PATCH v4 1/7] AMSO1100 Low Level Driver Steve Wise
2006-08-03 21:07 ` [PATCH v4 2/7] AMSO1100 WR / Event Definitions Steve Wise
2006-08-03 21:07 ` [PATCH v4 3/7] AMSO1100 OpenFabrics Provider Steve Wise
2006-08-03 21:07 ` [PATCH v4 4/7] AMSO1100 Memory Management Steve Wise
2006-08-03 21:07 ` [PATCH v4 5/7] AMSO1100 Message Queues Steve Wise
2006-08-03 21:07 ` [PATCH v4 6/7] AMSO1100: Privileged Verbs Queues Steve Wise
2006-08-03 21:07 ` [PATCH v4 7/7] AMSO1100 Makefiles and Kconfig changes Steve Wise
2006-08-28 23:07   ` Roland Dreier [this message]
2006-08-29  0:25     ` Steve Wise

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=adazmdoo3x8.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=netdev@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=swise@opengridcomputing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.