From: "David S. Miller" <davem@redhat.com>
To: Xose Vazquez Perez <xose@wanadoo.es>
Cc: jgarzik@redhat.com, netdev@oss.sgi.com, marcelo.tosatti@cyclades.com
Subject: Re: [PATCH] detailled bcm help-2.4.25
Date: Mon, 23 Feb 2004 09:54:54 -0800 [thread overview]
Message-ID: <20040223095454.488ace1f.davem@redhat.com> (raw)
In-Reply-To: <403A00AA.3010707@wanadoo.es>
On Mon, 23 Feb 2004 14:31:22 +0100
Xose Vazquez Perez <xose@wanadoo.es> wrote:
> aginst 2.4.25
>
> This patch adds more realistic information about bcm NICs.
> People only know the commercial names and not about chips names.
Please leave the tigon3, and say something like "tigon3 chips, also
commonly known as NetXtreme..." but even that is garbage because
3com and Alteon call the 57xx based products something else too.
This is why I really hate changes like this :)
prev parent reply other threads:[~2004-02-23 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 13:31 [PATCH] detailled bcm help-2.4.25 Xose Vazquez Perez
2004-02-23 17:54 ` David S. Miller [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=20040223095454.488ace1f.davem@redhat.com \
--to=davem@redhat.com \
--cc=jgarzik@redhat.com \
--cc=marcelo.tosatti@cyclades.com \
--cc=netdev@oss.sgi.com \
--cc=xose@wanadoo.es \
/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).