All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parthiban Veerasooran <parthiban.veerasooran@microchip.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
	<edumazet@google.com>, <pabeni@redhat.com>,
	<hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH net-next v3 0/4] net: microchip_t1s: fix collision detection on PLCA status change
Date: Fri, 25 Sep 2026 16:27:55 +0530	[thread overview]
Message-ID: <599985f5-219c-4158-b547-5b9c01ade449@microchip.com> (raw)
In-Reply-To: <20260924083355.5e839290@kernel.org>

Hi Jakub,

On 24/09/26 9:03 pm, Jakub Kicinski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On Fri, 18 Sep 2026 20:02:58 +0530 Parthiban Veerasooran wrote:
>> In a 10BASE-T1S multidrop network, the PHY autonomously transitions
>> between PLCA mode and CSMA/CD mode based on BEACON availability. The
>> existing collision detection logic only adjusted on explicit ethtool
>> PLCA changes, leaving it in the wrong state across these autonomous
>> transitions.
> 
> I'm going to assume at least one of the High or Medium severity
> findings is correct, please respond to the AI feedback in timely
> fashion, even if it's just to agree / tell us that v4 is coming.

Apologies for the delay. I had a quick look through the AI review 
feedback across all the patches, and it appears that some of the 
findings are valid and need to be addressed.

I am currently going through each comment and working on the necessary 
fixes. I will address all the valid review comments in v4 and submit the 
updated version as soon as possible.

Thank you for your patience.

Best regards,
Parthiban V> --
> pw-bot: cr


      reply	other threads:[~2026-09-25 10:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 14:32 [PATCH net-next v3 0/4] net: microchip_t1s: fix collision detection on PLCA status change Parthiban Veerasooran
2026-09-18 14:32 ` [PATCH net-next v3 1/4] net: phy: " Parthiban Veerasooran
2026-09-22 15:08   ` netdev-bot+sashiko
2026-09-18 14:33 ` [PATCH net-next v3 2/4] net: ethernet: oa_tc6: deliver the PHY interrupt to phylib Parthiban Veerasooran
2026-09-22 15:08   ` netdev-bot+sashiko
2026-09-18 14:33 ` [PATCH net-next v3 3/4] microchip: lan865x: enable PHY interrupt via virtual IRQ Parthiban Veerasooran
2026-09-22 15:08   ` netdev-bot+sashiko
2026-09-18 14:33 ` [PATCH net-next v3 4/4] net: phy: microchip_t1s: fix collision detection for LAN867X Rev.D0 Parthiban Veerasooran
2026-09-22 15:08   ` netdev-bot+sashiko
2026-09-24 15:33 ` [PATCH net-next v3 0/4] net: microchip_t1s: fix collision detection on PLCA status change Jakub Kicinski
2026-09-25 10:57   ` 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=599985f5-219c-4158-b547-5b9c01ade449@microchip.com \
    --to=parthiban.veerasooran@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew+netdev@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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.