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, Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH RFC v2 3/3] net: phy: allow EEE with SGMII interface modes
Date: Mon, 27 Mar 2017 23:47:28 +0100 [thread overview]
Message-ID: <20170327224728.GU7909@n2100.armlinux.org.uk> (raw)
In-Reply-To: <3bcc3380-6e59-06e3-9ebd-5450e89c90a2@gmail.com>
On Mon, Mar 27, 2017 at 03:42:57PM -0700, Florian Fainelli wrote:
> I think David will require you to resubmit this as an entire patch
> series and without an RFC tag. Do you want to hold off a bit to get
> build coverage or go ahead and target net-next right away?
I'd prefer to get build coverage first - there's no point in not using
the facilities that are available.
--
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-27 22:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 9:58 [PATCH RFC v2 0/3] phylib EEE updates Russell King - ARM Linux
2017-03-27 9:58 ` [PATCH RFC v2 1/3] net: phy: avoid setting unsupported EEE advertisments Russell King
2017-03-27 18:04 ` Florian Fainelli
2017-03-27 9:58 ` [PATCH RFC v2 2/3] net: phy: restart phy autonegotiation after EEE advertisment change Russell King
2017-03-27 18:03 ` Florian Fainelli
2017-03-27 9:59 ` [PATCH RFC v2 3/3] net: phy: allow EEE with SGMII interface modes Russell King
2017-03-27 16:47 ` Florian Fainelli
2017-03-27 17:00 ` Russell King - ARM Linux
2017-03-27 18:03 ` Florian Fainelli
2017-03-27 19:47 ` Russell King - ARM Linux
2017-03-27 19:48 ` Florian Fainelli
2017-03-27 20:15 ` Russell King - ARM Linux
2017-03-27 22:42 ` Florian Fainelli
2017-03-27 22:47 ` 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=20170327224728.GU7909@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--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).