From: Dave Jones <davej@redhat.com>
To: "Richard B. Johnson" <linux-os@analogic.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.6.12
Date: Tue, 21 Jun 2005 07:55:16 -0400 [thread overview]
Message-ID: <20050621115516.GC592@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0506210733430.9577@chaos.analogic.com>
On Tue, Jun 21, 2005 at 07:36:21AM -0400, Richard B. Johnson wrote:
> On Tue, 21 Jun 2005, Dave Jones wrote:
>
> >On Tue, Jun 21, 2005 at 07:17:55AM -0400, Richard B. Johnson wrote:
> >
> >> >> Bullshit. The source is available to anybody who wants it.
> >> >Great. Then please explain why you pull off this kind of crap..
> >> >(DataLink/license.c)
> >> Because it's true.
> >
> >kernel/module.c:1259 disagrees with you.
> >
> >static inline int license_is_gpl_compatible(const char *license)
> >{
> > return (strcmp(license, "GPL") == 0
> > || strcmp(license, "GPL v2") == 0
> > || strcmp(license, "GPL and additional rights") == 0
> > || strcmp(license, "Dual BSD/GPL") == 0
> > || strcmp(license, "Dual MPL/GPL") == 0);
> >}
> >
> >> >MODULE_LICENSE("GPL\0 They won't allow GPL/BSD anymore!");
> >
> >AFAICS, this is just plain deception. I suggest reading
> >http://marc.theaimsgroup.com/?l=linux-kernel&m=108304056922350&w=2
> >especially the part about talking to lawyers.
> >
> > Dave
> >
>
> At the time the work-around was inserted it was FACT.
According to the RCS file in the tarball you sent, license.c
was written on 2004.11.09.16.54.17;
It most certainly was around back then.
> I don't
> spend my time rewriting license strings to accommodate the
> whims of the latest GPL fanatic, thank you.
So I see. So instead you subvert the checks instead.
btw, text like this..
* # C O N F I D E N T I A L #
* # The information contained in or upon this document is the #
* # property of Analogic Corporation and is considered to be #
* # proprietary and may not be used by any recipient without #
* # the specific written permission of Analogic Corporation. #
Just fills me with confidence about the GPL'd nature of this driver.
Due to the "C O N F I D E N T I A L" nature of this driver, I've stopped
reading. Pity, datalink.c was quite amusing.
* Changed a lot of code to accommodate the stupid and sometimes
* downright wrong changes to the Linux kernel that occurred in
* Version 2.6.n.
*
* Yes. It's broken. I had to hard-code a bunch of stuff using
* "#define" where previously the kernel provided a logical
* value.
Dave
next prev parent reply other threads:[~2005-06-21 12:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 13:07 Linux-2.6.12 Richard B. Johnson
2005-06-20 13:48 ` Linux-2.6.12 Hugh Dickins
2005-06-20 14:22 ` Linux-2.6.12 Richard B. Johnson
2005-06-20 14:41 ` Linux-2.6.12 Hugh Dickins
2005-06-20 15:32 ` Linux-2.6.12 Richard B. Johnson
2005-06-20 16:02 ` Linux-2.6.12 Hugh Dickins
2005-06-21 0:32 ` Linux-2.6.12 Dave Jones
[not found] ` <Pine.LNX.4.61.0506210629110.8815@chaos.analogic.com>
2005-06-21 11:13 ` Linux-2.6.12 Dave Jones
2005-06-21 11:17 ` Linux-2.6.12 Richard B. Johnson
2005-06-21 11:30 ` Linux-2.6.12 Dave Jones
2005-06-21 11:36 ` Linux-2.6.12 Richard B. Johnson
2005-06-21 11:55 ` Dave Jones [this message]
2005-06-21 12:01 ` Linux-2.6.12 Richard B. Johnson
2005-06-21 12:15 ` Linux-2.6.12 Dave Jones
2005-06-21 12:30 ` Linux-2.6.12 Richard B. Johnson
2005-06-21 12:46 ` Linux-2.6.12 Dave Jones
2005-06-21 23:47 ` Linux-2.6.12 Kurt Wall
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=20050621115516.GC592@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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