linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Henning P. Schmiedehausen" <mailgate@hometree.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table
Date: Fri, 8 Jun 2001 08:29:02 +0000 (UTC)	[thread overview]
Message-ID: <9fq2ce$gkb$1@forge.intermeta.de> (raw)
In-Reply-To: <9fnjh0$d1c$1@forge.intermeta.de> <E1583xV-0001f3-00@the-village.bc.nu>

Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

>> And this is legal according to the "Kernel GPL, Linus Torvalds edition
>> (TM)" which says "any loadable module can be binary only". Not "only
>> loadable modules which are drivers". It may not be the intention but
>> it is the fact.

>Linus opinion on this is irrelevant. Neither I nor the FSF nor many others
>have released code under anything but the vanilla GPL. By merging such code
>Linus lost his ability to vary the license.

Ok, this is a new opinion, because it voids the "using the published
module ABI is unconditionally ok as stated again and again.

>So it comes down to the question of whether the module is linking (which is
>about dependancies and requirements) and what the legal scope is. Which
>is a matter for lawyers.

And this would void DaveMs' argument, that only the "official in
Linus' kernel published interface is allowed for binary modules". This
would mean, that putting the posted, unofficial patch under GPL into
the kernel and then using this interface for a binary module is just
the same as using only the official ABI from a lawyers' point of
view! 

This would make DaveMs' position even less understandable, because
there would be no difference for a proprietary vendor but keeping the
patch out of the kernel makes life harder for people like the original
poster that want to test new (open sourced) protocols like SCTP.

> Anyone releasing binary only modules does so having made their own
> appropriate risk assessment and having talked (I hope) to their
> insurers

Ugh, this is a sentence we're bound to read out of context on ZDNet
and m$.com... =:-( (Linux head developer warns companies to do risk
assessment before releasing drivers for Linux... Film at 11.)

	Regards
		Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen       -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH     hps@intermeta.de

Am Schwabachgrund 22  Fon.: 09131 / 50654-0   info@intermeta.de
D-91054 Buckenhof     Fax.: 09131 / 50654-20   

  reply	other threads:[~2001-06-08  8:29 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B1E5CC1.553B4EF1@alacritech.com>
2001-06-05 16:59 ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table La Monte H.P. Yarroll
2001-06-06 22:07   ` La Monte H.P. Yarroll
2001-06-07 19:11     ` Matthias Urlichs
2001-06-11 18:26   ` [PATCH] sockreg2.4.5-06 " La Monte H.P. Yarroll
2001-06-13 16:25   ` David S. Miller
2001-06-06 22:15 ` [PATCH] sockreg2.4.5-05 " David S. Miller
2001-06-06 22:36   ` Alexander Viro
2001-06-06 22:42   ` Richard Gooch
2001-06-06 22:52   ` David S. Miller
2001-06-06 23:21   ` Matt D. Robinson
2001-06-06 23:51     ` Richard Gooch
2001-06-07  0:51       ` David S. Miller
2001-06-07  5:37         ` George Bonser
2001-06-07  5:50         ` David S. Miller
2001-06-07  6:00           ` George Bonser
2001-06-07 15:18           ` watermodem
2001-06-07 15:51             ` Mike Galbraith
2001-06-09 22:09               ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregistertable watermodem
2001-06-09 23:15                 ` Alexander Viro
2001-06-10  2:59                 ` Horst von Brand
2001-06-10  4:38                 ` Mike Galbraith
2001-06-07  1:22       ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table Ben Greear
2001-06-07  5:16       ` Matt D. Robinson
2001-06-07 18:03         ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister Alan Cox
2001-06-07  5:46       ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table David S. Miller
2001-06-07  6:20       ` Richard Gooch
2001-06-07  6:47         ` Matt D. Robinson
2001-06-07 18:10     ` Alan Cox
2001-06-08  1:31     ` David S. Miller
2001-06-06 23:31   ` David S. Miller
2001-06-06 23:43   ` David S. Miller
2001-06-07 10:03     ` Henning P. Schmiedehausen
2001-06-07 10:50       ` Daniel Phillips
2001-06-07 17:52       ` Alan Cox
2001-06-08  8:29         ` Henning P. Schmiedehausen [this message]
2001-06-08 16:42           ` Alan Cox
2001-06-08 22:54           ` Albert D. Cahalan
2001-06-08 23:46             ` David Woodhouse
2001-06-11  8:45             ` Henning P. Schmiedehausen
2001-06-11  9:43               ` Helge Hafting
2001-06-11 16:17               ` Alan Cox
2001-06-11 18:31                 ` Jacob Luna Lundberg
2001-06-11 18:48                   ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister Alan Cox
2001-06-11 20:34                     ` Jacob Luna Lundberg
2001-06-12  7:08                   ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregistertable Helge Hafting
2001-06-07 10:05     ` [PATCH] sockreg2.4.5-05 inet[6]_create() register/unregister table Russell King
2001-06-07 15:27       ` Keith Owens
2001-06-07 17:01         ` David Woodhouse
2001-06-07 11:25     ` David S. Miller
2001-06-07 11:25     ` David S. Miller
2001-06-07  0:14   ` Ben Greear

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='9fq2ce$gkb$1@forge.intermeta.de' \
    --to=mailgate@hometree.net \
    --cc=hps@intermeta.de \
    --cc=linux-kernel@vger.kernel.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).