From: Andrew Lunn <andrew@lunn.ch>
To: Raju Lakkaraju <Raju.Lakkaraju@microchip.com>
Cc: netdev <netdev@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH RFC 00/13] Ethernet PHY cable test support
Date: Thu, 13 Jun 2019 15:06:18 +0200 [thread overview]
Message-ID: <20190613130618.GG23695@lunn.ch> (raw)
In-Reply-To: <20190613095748.GA27054@microsemi.com>
On Thu, Jun 13, 2019 at 03:28:04PM +0530, Raju Lakkaraju wrote:
> Hi Andrew,
>
> Look like these patches are not create from "net-next" branch.
Correct. As the cover note says, they are dependent on the work by
Michal Kubecek implementing ethtool-nl. He is currently using an older
tree, or at least he was when i forked his code.
> Can you please share branch detail where i can apply patches and check the code
> flow?
Yes, i can push out a branch, later today.
Andrew
next prev parent reply other threads:[~2019-06-13 15:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 16:05 [PATCH RFC 00/13] Ethernet PHY cable test support Andrew Lunn
2019-06-12 16:05 ` [PATCH RFC 01/13] net: phy: Add cable test support to state machine Andrew Lunn
2019-06-12 16:05 ` [PATCH RFC 02/13] net: phy: Add support for polling cable test Andrew Lunn
2019-06-12 16:05 ` [PATCH RFC 03/13] net: ethtool: netlink: Add support for triggering a " Andrew Lunn
2019-06-12 16:05 ` [PATCH RFC 04/13] net: ethtool: Add Properties for cable test reports Andrew Lunn
2019-06-12 16:05 ` [PATCH RFC 05/13] net: ethtool: Make helpers public Andrew Lunn
2019-06-12 16:05 ` [PATCH RFC 06/13] net: phy: Add infrastructure for reporting cable test results Andrew Lunn
2019-06-12 16:05 ` [PATCH RFC 07/13] net: phy: cable test: Use request seq in broadcast reply Andrew Lunn
2019-06-12 16:05 ` [PATCH RFC 08/13] net: phy: Add helpers for reporting test results Andrew Lunn
2019-06-12 16:05 ` [PATCH RFC 09/13] net: phy: marvell: Add cable test support Andrew Lunn
2019-06-13 3:08 ` Florian Fainelli
2019-06-12 16:05 ` [PATCH RFC 10/13] net: phy: Allow options to be passed to the cable test Andrew Lunn
2019-06-12 16:05 ` [PATCH RFC 11/13] net: phy: Add helpers and attributes for amplitude graph Andrew Lunn
2019-06-12 16:05 ` [PATCH RFC 12/13] net: phy: marvell: Add support " Andrew Lunn
2019-06-12 16:05 ` [PATCH RFC 13/13] net: phy: Put interface into oper testing during cable test Andrew Lunn
2019-06-13 9:58 ` [PATCH RFC 00/13] Ethernet PHY cable test support Raju Lakkaraju
2019-06-13 13:06 ` Andrew Lunn [this message]
2019-06-14 0:01 ` Andrew Lunn
2019-06-13 11:31 ` Raju Lakkaraju
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=20190613130618.GG23695@lunn.ch \
--to=andrew@lunn.ch \
--cc=Raju.Lakkaraju@microchip.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@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).