From: Andrew Lunn <andrew@lunn.ch>
To: "Das, Shubham" <shubham.das@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"maxime.chevallier@bootlin.com" <maxime.chevallier@bootlin.com>,
"alexander.duyck@gmail.com" <alexander.duyck@gmail.com>,
"lee@trager.us" <lee@trager.us>,
"D H, Siddaraju" <siddaraju.dh@intel.com>,
"Chintalapalle, Balaji" <balaji.chintalapalle@intel.com>,
"dasshubhamk@gmail.com" <dasshubhamk@gmail.com>,
"Lindberg, Magnus" <magnus.k.lindberg@ericsson.com>,
"Wirandi, Jonas" <jonas.wirandi@ericsson.com>
Subject: Re: [RFC net-next 0/2] ethtool: add interface caps and PHY tests
Date: Mon, 5 Oct 2026 15:43:01 +0200 [thread overview]
Message-ID: <a35f3ff2-6e57-4e97-a453-a7a9c725f723@lunn.ch> (raw)
In-Reply-To: <SN7PR11MB8109460641FC15211D8E7708FF962@SN7PR11MB8109.namprd11.prod.outlook.com>
> I can share ethtool command output and test logs demonstrating the API in use
> (PHY capability reporting, PHY test execution, etc.) if that would help validate the
> interface until the remaining dependencies and driver changes are posted upstream.
The code is not going to be merged until the driver side is ready. So
there is no rush.
Andrew
prev parent reply other threads:[~2026-10-05 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 13:21 [RFC net-next 0/2] ethtool: add interface caps and PHY tests Shubham Das
2026-09-30 13:21 ` [RFC net-next 1/2] ethtool: add interface capabilities query (intf-caps-get) Shubham Das
2026-09-30 13:53 ` Andrew Lunn
2026-10-05 4:10 ` Das, Shubham
2026-09-30 13:21 ` [RFC net-next 2/2] ethtool: add PHY test framework Shubham Das
2026-09-30 13:21 ` [RFC ethtool 0/2] add interface caps and PHY tests Shubham Das
2026-09-30 13:21 ` [RFC ethtool 1/2] ethtool: Add interface capability get support Shubham Das
2026-09-30 13:21 ` [RFC ethtool 2/2] ethtool: Add PHY test and BERT support Shubham Das
2026-09-30 13:58 ` [RFC net-next 0/2] ethtool: add interface caps and PHY tests Andrew Lunn
2026-10-05 4:13 ` Das, Shubham
2026-10-05 13:43 ` Andrew Lunn [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=a35f3ff2-6e57-4e97-a453-a7a9c725f723@lunn.ch \
--to=andrew@lunn.ch \
--cc=alexander.duyck@gmail.com \
--cc=balaji.chintalapalle@intel.com \
--cc=dasshubhamk@gmail.com \
--cc=jonas.wirandi@ericsson.com \
--cc=lee@trager.us \
--cc=magnus.k.lindberg@ericsson.com \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=shubham.das@intel.com \
--cc=siddaraju.dh@intel.com \
/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