From: Ariel Hendel <Ariel.Hendel@SUN.COM>
To: David Miller <davem@davemloft.net>
Cc: rick.jones2@hp.com, shemminger@linux-foundation.org,
netdev@vger.kernel.org, Greg.Onufer@SUN.COM, jeff@garzik.org,
Matheos.Worku@SUN.COM
Subject: Re: [PATCH]: Preliminary release of Sun Neptune driver
Date: Thu, 20 Sep 2007 09:06:20 -0700 [thread overview]
Message-ID: <46F29A7C.8040801@sun.com> (raw)
In-Reply-To: <20070919.165323.127197853.davem@davemloft.net>
Thanks Dave for your preliminary posting of the driver.
I am copying Matheos Worku. Matheos is intimately familiar with
the Neptune/NIU family of devices and their respective drivers.
Not only he can be a good reviewer, he can also clarify issues
around naming and so on. I agree that Neptune is just an overused
internal codename not worth propagating in the code.
Please feel free to add Matheos.Worku@Sun.COM to the reviewers list.
Ariel
David Miller wrote:
> From: Rick Jones <rick.jones2@hp.com>
> Date: Wed, 19 Sep 2007 16:20:39 -0700
>
>
>>so why "niu?" To what does niu translate anyway?
>
>
> Network Interface Unit. This is what the Niagara-2 programmers manual
> refers to the chip as.
>
> I try to name the files for most drivers I write as a 2 or 3 letter
> acronyms, it looks so much better than the usual verbose names. It's
> very unix.
prev parent reply other threads:[~2007-09-20 16:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 22:15 [PATCH]: Preliminary release of Sun Neptune driver David Miller
2007-09-19 21:59 ` Stephen Hemminger
2007-09-19 22:05 ` Jeff Garzik
2007-09-19 22:11 ` David Miller
2007-09-19 22:37 ` Jeff Garzik
2007-09-19 22:07 ` David Miller
2007-09-19 22:40 ` Jeff Garzik
2007-09-19 23:05 ` Stephen Hemminger
2007-09-19 23:17 ` David Miller
2007-09-19 23:20 ` Rick Jones
2007-09-19 23:53 ` David Miller
2007-09-20 16:06 ` Ariel Hendel [this message]
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=46F29A7C.8040801@sun.com \
--to=ariel.hendel@sun.com \
--cc=Greg.Onufer@SUN.COM \
--cc=Matheos.Worku@SUN.COM \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=shemminger@linux-foundation.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).