From: David Miller <davem@davemloft.net>
To: f.cachereul@alphalink.fr
Cc: rl@hellgate.ch, netdev@vger.kernel.org
Subject: Re: [PATCH] via-rhine: fix full-duplex with autoneg disable
Date: Thu, 12 Jun 2014 10:32:03 -0700 (PDT) [thread overview]
Message-ID: <20140612.103203.1223568534065505346.davem@davemloft.net> (raw)
In-Reply-To: <53997CCD.4010200@alphalink.fr>
From: François Cachereul <f.cachereul@alphalink.fr>
Date: Thu, 12 Jun 2014 12:11:25 +0200
> With some specific configuration (VT6105M on Soekris 5510 and depending
> on the device at the other end), fragmented packets were not transmitted
> when forcing 100 full-duplex with autoneg disable.
>
> This fix now write full-duplex chips register when forcing full or
> half-duplex not only when autoneg is enable.
>
> Signed-off-by: François Cachereul <f.cachereul@alphalink.fr>
Applied.
prev parent reply other threads:[~2014-06-12 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 10:11 [PATCH] via-rhine: fix full-duplex with autoneg disable François Cachereul
2014-06-12 17:32 ` 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=20140612.103203.1223568534065505346.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=f.cachereul@alphalink.fr \
--cc=netdev@vger.kernel.org \
--cc=rl@hellgate.ch \
/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).