From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH RFC] phylib EEE updates
Date: Mon, 27 Mar 2017 00:07:14 +0100 [thread overview]
Message-ID: <20170326230712.GA12597@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20170324111411.GD7909@n2100.armlinux.org.uk>
The 0-day builder identified some issues with the four RFC patches I
sent out before the weekend, I'll be sending v2 tomorrow. Sorry for
the noise.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2017-03-26 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 11:14 [PATCH RFC] phylib EEE updates Russell King - ARM Linux
2017-03-24 11:14 ` [PATCH RFC 1/3] net: phy: avoid setting unsupported EEE advertisments Russell King
2017-03-24 11:14 ` [PATCH RFC 2/3] net: phy: restart phy autonegotiation after EEE advertisment change Russell King
2017-03-24 11:14 ` [PATCH RFC 3/3] net: phy: allow EEE with SGMII interface modes Russell King
2017-03-26 23:07 ` Russell King - ARM Linux [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=20170326230712.GA12597@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.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).