From: <Parthiban.Veerasooran@microchip.com>
To: <andrew@lunn.ch>
Cc: <piergiorgio.beruto@gmail.com>, <hkallweit1@gmail.com>,
<linux@armlinux.org.uk>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 2/2] net: phy: microchip_t1s:: add cable diagnostic support for LAN867x Rev.D0
Date: Wed, 5 Nov 2025 04:39:45 +0000 [thread overview]
Message-ID: <a01ed5fb-c78d-4b5a-bf0f-b95893522cf9@microchip.com> (raw)
In-Reply-To: <3344ecef-3b45-42f7-b501-475413efbafe@lunn.ch>
On 04/11/25 9:18 pm, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
>> + .cable_test_start = genphy_c45_oatc14_cable_test_start,
>> + .cable_test_get_status =
>> + genphy_c45_oatc14_cable_test_get_status,
>
> netdev prefers lines at < 80, but up to 100 are accepted when they
> make sense. Please keep this on one lines.
Ok, thanks for the info. I will keep them in one line in the next
version. I mistakenly added the wrong cover letter subject line, so I’ve
already sent v2 to correct that. I’ll include this update in v3.
Best regards,
Parthiban V
>
> Andre
prev parent reply other threads:[~2025-11-05 4:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 10:20 [PATCH net-next 0/2] net: phy: microchip_t1s: Add support for LAN867x Rev.D0 PHY Parthiban Veerasooran
2025-11-04 10:20 ` [PATCH net-next 1/2] net: phy: phy-c45: add OATC14 10BASE-T1S PHY cable diagnostic support Parthiban Veerasooran
2025-11-04 15:46 ` Andrew Lunn
2025-11-05 4:37 ` Parthiban.Veerasooran
2025-11-04 10:20 ` [PATCH net-next 2/2] net: phy: microchip_t1s:: add cable diagnostic support for LAN867x Rev.D0 Parthiban Veerasooran
2025-11-04 15:48 ` Andrew Lunn
2025-11-05 4:39 ` Parthiban.Veerasooran [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=a01ed5fb-c78d-4b5a-bf0f-b95893522cf9@microchip.com \
--to=parthiban.veerasooran@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=piergiorgio.beruto@gmail.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
all inboxes | Powered by JetHome®