From: Auke Kok <auke-jan.h.kok@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Auke Kok <auke-jan.h.kok@intel.com>,
jakub@redhat.com, davem@redhat.com,
kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
john.ronciak@intel.com, jesse.brandeburg@intel.com
Subject: Re: e1000 driver contains private copy of GPL... and modified one, too
Date: Mon, 28 Aug 2006 14:33:23 -0700 [thread overview]
Message-ID: <44F36123.1000406@intel.com> (raw)
In-Reply-To: <20060828162539.GC30105@elf.ucw.cz>
Pavel Machek wrote:
> Hi!
>
>>> Okay, so modifications are not major: different address of free
>>> software foundation, completely different formatting, some characters
>>> added, and some characters removed. It no longer contains Linus'
>>> clarifications.
>>>
>>> --- LICENSE 2006-07-21 05:42:27.000000000 +0200
>>> +++ ../../../COPYING 2006-07-21 05:42:27.000000000 +0200
>>> @@ -1,128 +1,141 @@
>
>>> Now... I believe nothing evil is going on, but having two slightly
>>> different copies of GPL in one source seems wrong, can we get rid of
>>> e1000 one?
>> I'll ask around here and see if this doesn't make people cringe. Meanwhile
>> Pavel should examine sound/oss/COPYING and arch/sparc/lib/COPYING.LIB too :)
>
> Hehe, okay, going after them.
After discussing this with John and Jesse we found that we want to do an update
for all our drivers and fix the issue. I will send a patch later out that
removes the LICENSE file and changes the header of the involved files. I will
most likely have to do this for e100 and ixgb as well, so it will come a bit
later than right away.
Thanks Pavel.
Cheers,
Auke
prev parent reply other threads:[~2006-08-28 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 8:25 e1000 driver contains private copy of GPL... and modified one, too Pavel Machek
2006-08-28 15:26 ` Auke Kok
2006-08-28 16:25 ` Pavel Machek
2006-08-28 21:33 ` Auke Kok [this message]
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=44F36123.1000406@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=akpm@osdl.org \
--cc=davem@redhat.com \
--cc=jakub@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.