From: David Miller <davem@davemloft.net>
To: leitao@linux.vnet.ibm.com
Cc: klebers@linux.vnet.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH] ehea: fix wrongly reported speed and port
Date: Mon, 09 May 2011 11:49:32 -0700 (PDT) [thread overview]
Message-ID: <20110509.114932.112589716.davem@davemloft.net> (raw)
In-Reply-To: <4DC44487.4070207@linux.vnet.ibm.com>
From: Breno Leitao <leitao@linux.vnet.ibm.com>
Date: Fri, 06 May 2011 15:57:11 -0300
> On 05/04/2011 08:05 PM, Kleber Sacilotto de Souza wrote:
>> Currently EHEA reports to ethtool as supporting 10M, 100M, 1G and
>> 10G and connected to FIBRE independent of the hardware configuration.
>> However, when connected to FIBRE the only supported speed is 10G
>> full-duplex, and the other speeds and modes are only supported
>> when connected to twisted pair.
>>
>> Signed-off-by: Kleber Sacilotto de Souza <klebers@linux.vnet.ibm.com>
> Acked-by: Breno Leitao <leitao@linux.vnet.ibm.com>
Applied, thanks.
prev parent reply other threads:[~2011-05-09 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 23:05 [PATCH] ehea: fix wrongly reported speed and port Kleber Sacilotto de Souza
[not found] ` <4DC44487.4070207@linux.vnet.ibm.com>
2011-05-09 18:49 ` David 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=20110509.114932.112589716.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=klebers@linux.vnet.ibm.com \
--cc=leitao@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).