mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Sean Hefty <sean.hefty@intel.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	openib-general@openib.org
Subject: Re: [PATCH 2/5] [RFC] Infiniband: connection abstraction
Date: Wed, 18 Jan 2006 08:08:26 +0100	[thread overview]
Message-ID: <1137568107.3005.69.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060117153838.3dc2cd2e@dxpl.pdx.osdl.net>


> 
> <flamebait>
> Also should infiniband exports be EXPORT_SYMBOL_GPL, to make
> it clear that binary drivers for this are not allowed??
> </flamebait>

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).




  parent reply	other threads:[~2006-01-18  7:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 23:16 [PATCH 0/5] " 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:38   ` Stephen Hemminger
2006-01-17 23:51     ` Sean Hefty
2006-01-18  7:08     ` Arjan van de Ven [this message]
2006-01-18 20:27       ` Bryan O'Sullivan
2006-01-18  2:03   ` [openib-general] " 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:28 ` [PATCH 3/5] " Sean Hefty
2006-01-21 23:37   ` [openib-general] " Roland Dreier
2006-01-17 23:37 ` [PATCH 4/5] " Sean Hefty
2006-01-17 23:44 ` [PATCH 5/5] " Sean Hefty
2006-01-18 15:43   ` [openib-general] " Roland Dreier
2006-01-18 15:44   ` Roland Dreier
2006-01-18 18:19     ` Sean Hefty
2006-01-18 18:49       ` 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=1137568107.3005.69.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=sean.hefty@intel.com \
    --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

all inboxes | Powered by JetHome®