From: Ion Badulescu <ionut@moisil.cs.columbia.edu>
To: Riley Williams <rhw@MemAlpha.CX>
Cc: Shawn Starr <spstarr@sh0n.net>, <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T
Date: Wed, 13 Jun 2001 03:25:22 -0700 [thread overview]
Message-ID: <200106131025.f5DAPMF01441@moisil.badula.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0106121818030.30835-100000@infradead.org>
On Tue, 12 Jun 2001 18:20:58 +0100 (BST), Riley Williams <rhw@memalpha.cx> wrote:
> Shawn, I'd suggest you tell the said sales guy that IF he can get you
> the FULL specs TOGETHER WITH permission to freely distribute them, AND
Permission to freely distribute the specs isn't necessary, although it
is nice indeed. All that's needed is permission to GPL the driver sources
written using knowledge from said specs.
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
next prev parent reply other threads:[~2001-06-13 10:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 17:37 softirq bugs in pre2 Andrea Arcangeli
2001-06-11 19:09 ` Linus Torvalds
2001-06-11 19:41 ` Andrea Arcangeli
2001-06-11 20:55 ` Alan Cox
2001-06-11 22:42 ` Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T Shawn Starr
2001-06-12 16:34 ` Alan Cox
2001-06-12 17:20 ` Riley Williams
2001-06-13 10:25 ` Ion Badulescu [this message]
2001-06-13 12:40 ` Ralf Baechle
2001-06-13 17:07 ` James Sutherland
2001-06-14 20:59 ` Riley Williams
2001-06-14 21:10 ` Jeff Garzik
2001-06-14 21:14 ` Matthew Jacob
2001-06-14 21:29 ` Alan Cox
2001-06-14 21:52 ` Matthew Dharm
2001-06-14 21:58 ` Alan Cox
2001-06-14 22:03 ` Matthew Jacob
2001-06-15 2:20 ` Shawn Starr
2001-06-12 2:54 ` softirq bugs in pre2 Andrew Morton
2001-06-11 21:58 ` Pavel Machek
[not found] <200106112259.RAA20183@asooo.flowerfire.com>
2001-06-12 0:39 ` Gigabit Intel NIC? - Intel Gigabit Ethernet Pro/1000T Shawn Starr
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=200106131025.f5DAPMF01441@moisil.badula.org \
--to=ionut@moisil.cs.columbia.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rhw@MemAlpha.CX \
--cc=spstarr@sh0n.net \
/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