From: spam@systol-ng.god.lan
To: Hans Petter Selasky <hselasky@c2i.net>
Cc: Henk.Vergonet@gmail.com, licensing@fsf.org, linux-kernel@vger.kernel.org
Subject: Re: Yealink driver
Date: Wed, 28 Oct 2009 17:17:22 +0100 [thread overview]
Message-ID: <20091028161722.GA30039@systol-ng.god.lan> (raw)
In-Reply-To: <200910262115.41869.hselasky@c2i.net>
On Mon, Oct 26, 2009 at 09:15:40PM +0100, Hans Petter Selasky wrote:
> On Monday 26 October 2009 18:12:04 spam@systol-ng.god.lan wrote:
> > On Sat, Oct 10, 2009 at 08:12:50PM +0200, Hans Petter Selasky wrote:
> > > Hi,
> > >
> > > I'm about to port your Yealink driver in Linux to FreeBSD (ISDN4BSD)
> > > under a 2 clause BSD license. Your Yealink driver will be used as a
> > > hardware reference document. Hope that is OK by you.
> > >
> > > I will send you an e-mail when the porting is complete with the source
> > > code
> > >
> > > :-)
> > >
> > > --HPS
> >
> > Hmm,
> >
> > The driver is released under GPL2 for good reasons, I object to a
> > re-license under a BSD or any other "free beer" type of license.
> >
>
> Hi,
>
> I'm not asking about re-licensing the whole driver, I think you misunderstand.
> I'm asking for permission to copy some programming commands so that I can use
> my Yealink under ISDN4BSD. Where did you get the documentation from, in
> between?
>
Ok there's no problem in using the code as a reference. I only want to
avoid my code being reused in proprietary implementations, as is
possible with BSD licensing.
Regards,
Henk
prev parent reply other threads:[~2009-10-28 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200910102012.51666.hselasky@c2i.net>
2009-10-26 17:12 ` spam
2009-10-26 20:15 ` Hans Petter Selasky
2009-10-28 16:17 ` spam [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=20091028161722.GA30039@systol-ng.god.lan \
--to=spam@systol-ng.god.lan \
--cc=Henk.Vergonet@gmail.com \
--cc=hselasky@c2i.net \
--cc=licensing@fsf.org \
--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
all inboxes | Powered by JetHome®