From: David Miller <davem@davemloft.net>
To: rmk+kernel@arm.linux.org.uk
Cc: netdev@vger.kernel.org, andrew@lunn.ch, linux@roeck-us.net
Subject: Re: [PATCH] net: dsa: mv88e6xxx: remove link polling
Date: Wed, 07 Oct 2015 02:59:07 -0700 (PDT) [thread overview]
Message-ID: <20151007.025907.365366822224236229.davem@davemloft.net> (raw)
In-Reply-To: <E1ZiQIv-0003pw-Ur@rmk-PC.arm.linux.org.uk>
From: Russell King <rmk+kernel@arm.linux.org.uk>
Date: Sat, 03 Oct 2015 18:09:01 +0100
> The link status is polled by the generic phy layer, there's no need to
> duplicate that polling with additional polling. This additional polling
> adds additional MDIO traffic, and races with the generic phy layer,
> resulting in missing or duplicated link status messages.
>
> Tested-by: Andrew Lunn <andrew@lunn.ch>
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Applied.
prev parent reply other threads:[~2015-10-07 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 17:09 [PATCH] net: dsa: mv88e6xxx: remove link polling Russell King
2015-10-07 9:59 ` 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=20151007.025907.365366822224236229.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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).