From: Kalle Valo <Kalle.Valo@iki.fi>
To: Harald Welte <laforge@gnumonks.org>
Cc: kernel-mentors@selenic.com, netdev <netdev@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: atheros driver - desc
Date: Sun, 07 Aug 2005 10:32:07 +0300 [thread overview]
Message-ID: <87pssqp5hk.fsf@litku.valo.iki.fi> (raw)
In-Reply-To: <20050806214544.GA4594@rama.de.gnumonks.org> (Harald Welte's message of "Sat, 6 Aug 2005 23:45:44 +0200")
Harald Welte <laforge@gnumonks.org> writes:
> I don't want to turn this list into a list of legal discussion, but
> since I'm heavily dealing with exactly those issues during my
> gpl-violations.org efforts, I thought I share some of the facts.
Thanks for your answer, it cleared up things. I also don't want to
discuss legal things here, we can discuss it more privately. But I'll
just ask one more question in public:
> So in general, at least if you're doing that kind of work within the EU,
> I wouldn't be worried all that much.
That's good news. But what about inclusion to the official Linux
kernel? Can a driver reverse-engineered in EU be included to the
kernel? (Big part of Linux is developed in US, I guess.)
--
Kalle Valo
next prev parent reply other threads:[~2005-08-07 7:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 2:55 atheros driver - desc Mateusz Berezecki
2005-08-05 10:14 ` Michael Renzmann
2005-08-05 16:46 ` Bryan O'Sullivan
2005-08-05 17:46 ` Jeff Garzik
2005-08-06 19:57 ` Kalle Valo
2005-08-06 20:53 ` Jeff Garzik
2005-08-06 21:45 ` Harald Welte
2005-08-07 7:32 ` Kalle Valo [this message]
2005-08-07 15:01 ` Harald Welte
2005-08-12 7:37 ` Chris Wedgwood
2005-08-12 11:45 ` Harald Welte
2005-08-25 16:36 ` [OT] legal status of re-engineering (was Re: atheros driver - desc) Harald Welte
2005-08-06 21:38 ` atheros driver - desc Mateusz Berezecki
-- strict thread matches above, loose matches on Subject: below --
2005-08-05 18:07 Mateusz Berezecki
2005-08-05 18:39 ` Jeff Garzik
2005-08-05 18:54 ` Mateusz Berezecki
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=87pssqp5hk.fsf@litku.valo.iki.fi \
--to=kalle.valo@iki.fi \
--cc=jgarzik@pobox.com \
--cc=kernel-mentors@selenic.com \
--cc=laforge@gnumonks.org \
--cc=netdev@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).