From: Jeff Garzik <jeff@garzik.org>
To: Reyk Floeter <reyk@openbsd.org>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, jirislaby@gmail.com,
moglen@softwarefreedom.org
Subject: Re: request for information about the "ath5k" licensing
Date: Fri, 07 Sep 2007 19:42:36 -0400 [thread overview]
Message-ID: <46E1E1EC.4000405@garzik.org> (raw)
In-Reply-To: <20070907064730.GA15001@slim.vantronix.net>
Reyk Floeter wrote:
> I'm still waiting for an answer. Your process is taking too long.
Speaking as a person through which these changes flow upstream into the
official kernel (ath5k maintainers -> linville -> me -> linus)...
The most important thing for today is that no ath5k stuff has been
committed (nor has it ever been).
I would rather take it slow and make sure everybody is happy. There is
nothing upstream, and so, there is no need to rush and correct something.
Collectively, this is just growing pains. Everyone is breaking new
ground, trying to figure out how to best support atheros stuff on Linux.
There are new tools to deal with (svn? git? flavor of the day?:)), new
licenses with new ramifications to consider, a new wireless stack to
deal with.
What you are witnessing is but a small part of the chaos as everyone
tackles these chores simultaneously.
Jeff
next prev parent reply other threads:[~2007-09-07 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070905151823.GA1384@slim.vantronix.net>
[not found] ` <200709051835.33572.mb@bu3sch.de>
[not found] ` <43e72e890709051000m74252604paff3eb1651f55d22@mail.gmail.com>
2007-09-07 6:47 ` request for information about the "ath5k" licensing Reyk Floeter
2007-09-07 23:42 ` Jeff Garzik [this message]
2007-09-05 15:48 Reyk Floeter
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=46E1E1EC.4000405@garzik.org \
--to=jeff@garzik.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=moglen@softwarefreedom.org \
--cc=netdev@vger.kernel.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).