From: Jeff Garzik <jgarzik@pobox.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.4] forcedeth
Date: Sat, 08 Nov 2003 12:55:16 -0500 [thread overview]
Message-ID: <3FAD2E04.3020800@pobox.com> (raw)
In-Reply-To: <20031108085415.C18856@infradead.org>
Christoph Hellwig wrote:
> On Sat, Nov 08, 2003 at 06:47:43AM +0100, Carl-Daniel Hailfinger wrote:
>
>>Attached is forcedeth: A new driver for the ethernet interface of the
>>NVIDIA nForce chipset, licensed under GPL.
>
>
> Any chance to give the driver a more descriptive name, say nforce_eth?
> Traditionally we tend to name like drivers after the hardware's name or
> codename, not the development methology used.
I agree with you on this -- but -- in this special case, it seems wise
to avoid using a potential trademark as a filename...
I would prefer to avoid the issue completely, rather have to chase down
some lawyers and get a definitive answer.
Jeff
next prev parent reply other threads:[~2003-11-08 17:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-08 5:47 [PATCH 2.4] forcedeth Carl-Daniel Hailfinger
2003-11-08 8:54 ` Christoph Hellwig
2003-11-08 10:51 ` Krzysztof Halasa
2003-11-08 17:55 ` Jeff Garzik [this message]
2003-11-08 20:23 ` Carl-Daniel Hailfinger
2003-11-09 0:15 ` Zwane Mwaikambo
2003-11-08 17:39 ` Jeff Garzik
2003-11-08 20:26 ` Markus Hästbacka
2003-11-08 20:59 ` Valdis.Kletnieks
2003-11-08 21:38 ` Markus Hästbacka
2003-11-09 12:36 ` Carl-Daniel Hailfinger
2003-11-09 14:07 ` Markus Hästbacka
-- strict thread matches above, loose matches on Subject: below --
2003-11-09 9:47 Manfred Spraul
2003-11-09 14:14 ` Markus Hästbacka
2003-11-09 14:47 ` Manfred Spraul
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=3FAD2E04.3020800@pobox.com \
--to=jgarzik@pobox.com \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=hch@infradead.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