From: Michael Buesch <mb@bu3sch.de>
To: Reyk Floeter <reyk@openbsd.org>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-netdev@vger.kernel.org, jirislaby@gmail.com,
moglen@softwarefreedom.org, mcgrof@gmail.com
Subject: Re: request for information about the "ath5k" licensing
Date: Wed, 5 Sep 2007 18:35:33 +0200 [thread overview]
Message-ID: <200709051835.33572.mb@bu3sch.de> (raw)
In-Reply-To: <20070905151823.GA1384@slim.vantronix.net>
On Wednesday 05 September 2007, Reyk Floeter wrote:
> I'm the author of the free hardware driver layer for wireless Atheros
> devices in OpenBSD, also known as "OpenHAL".
>
> I'm still trying to get an idea about the facts and the latest state
> of the incidence that violated the copyright of my code, because I
> just returned from vacation.
> Could you please give me some feedback about the latest state? Please
> reply in private, I'm not subscribed to any of the Linux lists and I'm
> rather interested in facts than in the usual trolling.
>
> - Has this issue been fixed?
It has never been applied to any repository.
-> No issue and no copyright violation.
> - Is there any repository available with the "ath5k" code using a
> modified/"extended" license?
No.
> I don't know how to find the relevant bits in the various Linux git
> repositories. Sorry, I don't get the structure of it. Are there any
> other sources online except this diff on the linux kernel mailing
> list?
>
> - Are there any plans to release the "ath5k" code using a
> modified/"extended" license?
No.
next prev parent reply other threads:[~2007-09-05 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 15:18 request for information about the "ath5k" licensing Reyk Floeter
2007-09-05 16:35 ` Michael Buesch [this message]
2007-09-05 17:00 ` Luis R. Rodriguez
2007-09-07 6:47 ` Reyk Floeter
2007-09-07 23:42 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2007-09-07 8:20 Joerg Pommnitz
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=200709051835.33572.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-netdev@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=moglen@softwarefreedom.org \
--cc=reyk@openbsd.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).