From: Krzysztof Halasa <khc@pm.waw.pl>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, netdev <netdev@vger.kernel.org>
Subject: Re: [RFC] Expanding ethtool PHY information
Date: Wed, 14 Jan 2009 18:01:46 +0100 [thread overview]
Message-ID: <m3fxjles91.fsf@maximus.localdomain> (raw)
In-Reply-To: <1231879514.3005.31.camel@achroite> (Ben Hutchings's message of "Tue\, 13 Jan 2009 20\:45\:14 +0000")
Ben Hutchings <bhutchings@solarflare.com> writes:
> The set of port types reported through the ethtool API is looking a bit
> limited:
>
> /* Which connector port. */
> #define PORT_TP 0x00
> #define PORT_AUI 0x01
> #define PORT_MII 0x02
> #define PORT_FIBRE 0x03
> #define PORT_BNC 0x04
Perhaps using an ASCII string would be a better approach? Leaving the
old one for compatibility of course.
--
Krzysztof Halasa
prev parent reply other threads:[~2009-01-14 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 20:45 [RFC] Expanding ethtool PHY information Ben Hutchings
2009-01-14 16:55 ` Jeff Garzik
2009-01-14 17:01 ` Krzysztof Halasa [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=m3fxjles91.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=bhutchings@solarflare.com \
--cc=jgarzik@pobox.com \
--cc=netdev@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