From: Ben Hutchings <bhutchings@solarflare.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: Anthony DeRobertis <anthony@derobert.net>,
netdev <netdev@vger.kernel.org>,
e1000-devel@lists.sourceforge.net, 574574@bugs.debian.org
Subject: Re: Support e1000 M88 PHY registers in -d
Date: Mon, 04 Apr 2011 10:41:42 +0100 [thread overview]
Message-ID: <1301910102.2935.52.camel@localhost> (raw)
In-Reply-To: <BANLkTik7G82DwhA_EU8KrKJO25+W=yjWFg@mail.gmail.com>
On Mon, 2011-04-04 at 01:36 -0700, Jeff Kirsher wrote:
> On Sat, Apr 2, 2011 at 09:24, Ben Hutchings <bhutchings@solarflare.com> wrote:
> > Anthony,
> >
> > I'm now upstream maintainer for ethtool so I've picked up your patch
> > again.
> >
> > On Fri, 2010-03-19 at 00:32 -0400, Anthony DeRobertis wrote:
> >> Package: ethtool
> >> Version: 1:2.6.33-1
> >> Severity: wishlist
> >>
> >> The M88 PHY registers contain useful information like the cable length
> >> estimate and the MDI/MDIX status. The attached patch makes -d dump
> >> them.
> >
> > Patches for ethtool should include a commit message and Signed-off-by
> > line, as in the Linux kernel. See sections 2 and 12 of
> > <http://www.kernel.org/doc/Documentation/SubmittingPatches>. They
> > should be sent to this address and to netdev.
> >
> > I'm forwarding this patch to netdev and the e1000 developers for review.
> >
> > Ben.
>
> Thanks Ben. Just to be clear, have you applied these e1000 changes to
> the ethtool?
[...]
I have not applied these changes either anywhere.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-04-04 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100319043229.24908.99968.reportbug@Feynman.home>
2011-04-02 16:24 ` Support e1000 M88 PHY registers in -d Ben Hutchings
2011-04-04 8:36 ` Jeff Kirsher
2011-04-04 9:41 ` Ben Hutchings [this message]
2011-05-04 17:41 ` Ben Hutchings
2011-05-04 18:00 ` Jeff Kirsher
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=1301910102.2935.52.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=574574@bugs.debian.org \
--cc=anthony@derobert.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.