LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Zan Lynx <zlynx@acm.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jon Masters <jcm@jonmasters.org>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only symbols
Date: Fri, 29 Feb 2008 16:13:34 -0500 [thread overview]
Message-ID: <1204319614.2316.39.camel@dv> (raw)
In-Reply-To: <alpine.LFD.1.00.0802291224290.17889@woody.linux-foundation.org>
On Fri, 2008-02-29 at 12:28 -0800, Linus Torvalds wrote:
>
> On Fri, 29 Feb 2008, Pavel Roskin wrote:
> >
> > This still leaves us with the workqueue interface:
> >
> > __create_workqueue_key
> > destroy_workqueue
> > flush_workqueue
> > queue_work
>
> Hmm. Personally, I don't see those as being a big issue, but they've been
> marked GPL-only for a long while.
>
> The thing is, I personally don't mind, and I think "derived code" is what
> matters, but others disagree, and quite frankly, I'm not going to force
> them - I have my _personal_ beliefs, but hey, others have theirs.
>
> So you really need to talk to not me, but to the people who actually wrote
> and maintain that code.
As far as I can tell, those people have never tried to prevent
ndiswrapper from using their code. Both times ndiswrapper was prevented
from using GPLONLY symbols, it was done unintentionally.
> When they come back and say "yeah, we think
> ndiswrapper is a special case and we're ok with it", I'll happily either
> mark those things non-GPL or just mark ndiswrapper special in the module
> loader again.
OK, I'll keep it in mind in case such approach actually becomes
necessary.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-02-29 21:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 22:11 Pavel Roskin
2008-02-28 23:25 ` Linus Torvalds
2008-02-29 6:20 ` Pavel Roskin
2008-02-29 16:08 ` Linus Torvalds
2008-02-29 16:54 ` Chris Friesen
2008-02-29 17:06 ` Linus Torvalds
2008-02-29 17:59 ` Chris Friesen
2008-03-06 14:56 ` David Woodhouse
2008-02-29 16:59 ` Zan Lynx
2008-02-29 17:07 ` Linus Torvalds
2008-02-29 17:20 ` Pavel Roskin
2008-02-29 17:33 ` Linus Torvalds
2008-02-29 19:39 ` Pavel Roskin
2008-02-29 19:53 ` Linus Torvalds
2008-02-29 20:08 ` Pavel Roskin
2008-02-29 20:28 ` Linus Torvalds
2008-02-29 21:13 ` Pavel Roskin [this message]
2008-02-29 20:17 ` John W. Linville
2008-02-29 20:40 ` David Newall
2008-02-29 20:59 ` Pavel Roskin
2008-02-29 21:08 ` David Newall
2008-02-29 22:17 ` Pavel Roskin
2008-03-01 8:15 ` David Newall
2008-02-29 20:44 ` Pavel Roskin
2008-02-29 21:15 ` Ingo Molnar
2008-02-29 22:31 ` Pavel Roskin
2008-03-03 10:57 ` Ingo Molnar
2008-03-04 5:37 ` Pavel Roskin
2008-03-04 12:57 ` Ingo Molnar
2008-03-04 17:19 ` Linus Torvalds
2008-03-04 17:38 ` Greg KH
2008-03-04 17:45 ` Pavel Roskin
2008-03-04 21:20 ` Ingo Molnar
2008-03-04 23:23 ` Pavel Roskin
2008-03-04 20:51 ` Ingo Molnar
2008-03-04 23:25 ` Jiri Kosina
2008-03-05 13:21 ` Ingo Molnar
2008-02-29 17:18 ` Jon Masters
2008-02-29 21:55 ` Adrian Bunk
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=1204319614.2316.39.camel@dv \
--to=proski@gnu.org \
--cc=jcm@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.org \
--cc=zlynx@acm.org \
--subject='Re: [PATCH 2.6.25] module: allow ndiswrapper to use GPL-only symbols' \
/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
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).