netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan O'Sullivan <bos@serpentine.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: netdev@vger.kernel.org, openib-general@openib.org,
	linux-kernel@vger.kernel.org,
	Stephen Hemminger <shemminger@osdl.org>
Subject: Re: [PATCH 2/5] [RFC] Infiniband: connection abstraction
Date: Wed, 18 Jan 2006 12:27:32 -0800	[thread overview]
Message-ID: <1137616052.4757.85.camel@serpentine.pathscale.com> (raw)
In-Reply-To: <1137568107.3005.69.camel@laptopd505.fenrus.org>

On Wed, 2006-01-18 at 08:08 +0100, Arjan van de Ven wrote:

> the dual license text needs a bit of clarification I suspect to make
> explicit that the "or BSD" part only applies when used entirely outside
> the linux kernel. (that already is the case, just it's not explicit.
> Making that explicit would be good).

One appropriate way to do that would be to mark all IB-related exported
symbols as EXPORT_SYMBOL_GPL.

	<b

  reply	other threads:[~2006-01-18 20:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 23:16 [PATCH 0/5] [RFC] Infiniband: connection abstraction Sean Hefty
2006-01-17 23:21 ` [PATCH 1/5] " Sean Hefty
2006-01-17 23:24 ` [PATCH 2/5] " Sean Hefty
2006-01-17 23:28 ` [PATCH 3/5] " Sean Hefty
2006-01-21 23:37   ` Roland Dreier
2006-01-17 23:37 ` [PATCH 4/5] " Sean Hefty
     [not found] ` <ORSMSX401FRaqbC8wSA00000040@orsmsx401.amr.corp.intel.com>
2006-01-17 23:38   ` [PATCH 2/5] " Stephen Hemminger
2006-01-17 23:51     ` Sean Hefty
2006-01-18  7:08     ` Arjan van de Ven
2006-01-18 20:27       ` Bryan O'Sullivan [this message]
2006-01-18  2:03   ` Grant Grundler
2006-01-18 17:46     ` Sean Hefty
2006-01-18 18:02       ` Grant Grundler
2006-01-18 18:13         ` Sean Hefty
2006-01-17 23:44 ` [PATCH 5/5] " Sean Hefty
2006-01-18 15:43   ` Roland Dreier
2006-01-18 15:44   ` Roland Dreier
2006-01-18 18:19     ` Sean Hefty
2006-01-18 18:49       ` [openib-general] " Grant Grundler

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=1137616052.4757.85.camel@serpentine.pathscale.com \
    --to=bos@serpentine.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=shemminger@osdl.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).