From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Chris Friesen <chris.friesen@genband.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: MODULE_LICENSE("GPL")??
Date: Fri, 03 Aug 2012 08:04:21 -0400 [thread overview]
Message-ID: <501BBE45.8060309@cfl.rr.com> (raw)
In-Reply-To: <501B5D51.5030307@genband.com>
On 08/03/2012 01:10 AM, Chris Friesen wrote:
> On 08/02/2012 06:19 AM, Mark Hounschell wrote:
>>
>> This particular driver does in fact build cleanly after changing the GPL
>> to PROPRIETARY. I haven't actually purchased the product yet so am unable
>> to load it, but can I assume that if I don't have a build issue when
>> specifying PROPRIETARY, that they are in fact NOT using GPL symbols and
>> maybe they just thought they needed to specify GPL for some reason or
>> another?
>
> Why not just ask the authors?
>
Well, I will before I actually distribute it to anyone. It's still not set
in stone that I'm going to use their product but since I now know that it
at least builds as NOT GPL, I just thought someone here could confirm my
assumption that that actually meant they were NOT using GPL symbols.
Thanks
Mark
next prev parent reply other threads:[~2012-08-03 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 21:24 MODULE_LICENSE("GPL")?? Mark Hounschell
2012-08-01 21:42 ` MODULE_LICENSE("GPL")?? Chris Friesen
2012-08-01 21:43 ` MODULE_LICENSE("GPL")?? Alan Cox
2012-08-02 12:19 ` MODULE_LICENSE("GPL")?? Mark Hounschell
2012-08-03 5:10 ` MODULE_LICENSE("GPL")?? Chris Friesen
2012-08-03 12:04 ` Mark Hounschell [this message]
2012-08-03 13:29 ` MODULE_LICENSE("GPL")?? Alan Cox
2012-08-03 14:10 ` MODULE_LICENSE("GPL")?? Mark Hounschell
2012-08-03 14:20 ` MODULE_LICENSE("GPL")?? Alan Cox
2012-08-03 18:19 ` MODULE_LICENSE("GPL")?? Theodore Ts'o
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=501BBE45.8060309@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chris.friesen@genband.com \
--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).