From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
To: "Paul Rolland" <rol@witbe.net>, "Jeff Garzik" <jgarzik@pobox.com>
Cc: "Jesper Juhl" <jesper.juhl@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
cramerj@intel.com, john.ronciak@intel.com
Subject: Re: [2.4.32 - 2.6.15.4] e1000 - Fix mii interface
Date: Mon, 27 Feb 2006 11:26:12 -0800 [thread overview]
Message-ID: <4807377b0602271126s39285884gd0e1c51c14b5d6a7@mail.gmail.com> (raw)
In-Reply-To: <01e101c63ae7$1b417990$2001a8c0@cortex>
On 2/26/06, Paul Rolland <rol@witbe.net> wrote:
> Hello,
>
> > Ok, great, I was just wondering since I would have made one if you had
> > no plans to do so.
>
> Well, I was just waiting to make sure it was interesting for someone ;)
>
> Here is it, verified with tab and not spaces... but attached as my mailer
> is likely to cripple anything I try to inline...
>
> Signed-off-by: Paul Rolland <rol@as2917.net>
I've got an issue with this, as the same function is called in
e1000_ethtool.c. I think the correct fix is to fix the caller in the
mii-tool case, but I am working on verifiying my assumptions.
In the meantime can you send the exact command you were having the problem with?
next prev parent reply other threads:[~2006-02-27 19:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060225085409.GA22456@infradead.org>
2006-02-25 10:08 ` [2.4.32 - 2.6.15.4] e1000 - Fix mii interface Paul Rolland
2006-02-26 10:42 ` Willy TARREAU
2006-02-26 11:39 ` Paul Rolland
2006-02-26 12:59 ` Jesper Juhl
2006-02-26 14:55 ` Paul Rolland
2006-02-26 15:00 ` Jesper Juhl
2006-02-26 15:12 ` Paul Rolland
2006-02-27 19:26 ` Jesse Brandeburg [this message]
[not found] ` <4807377b0602271234v4b6cdeecpbcf8d4a6ac51cd20@mail.gmail.com>
2006-02-28 2:31 ` Jesse Brandeburg
2006-02-28 10:46 ` Paul Rolland
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=4807377b0602271126s39285884gd0e1c51c14b5d6a7@mail.gmail.com \
--to=jesse.brandeburg@gmail.com \
--cc=cramerj@intel.com \
--cc=jesper.juhl@gmail.com \
--cc=jgarzik@pobox.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rol@witbe.net \
/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).