All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saivarun Mudepally <saivarun@couthit.com>
To: netdev-bot+sinfo@kernel.org
Cc: Sai Varun Mudepally <saivarun@couthit.com>,
	danishanwar@ti.com,  parvathi@couthit.com, rogerq@kernel.org,
	pmohan@couthit.com,  andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@kernel.org,  kuba@kernel.org, pabeni@redhat.com,
	afd@ti.com,  basharath@couthit.com, horms@kernel.org,
	 linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
	 linux-kernel@vger.kernel.org, pratheesh@ti.com, vigneshr@ti.com,
	 praneeth@ti.com, srk@ti.com, j-rameshbabu@ti.com,
	m-malladi@ti.com,  rogerq@ti.com, krishna@couthit.com,
	mohan@couthit.com
Subject: Re: [PATCH net-next] net: ti: icssm-prueth: use dev_close()/dev_open() in icssm_prueth_change_mode()
Date: Mon, 19 Oct 2026 15:54:21 +0530 (IST)	[thread overview]
Message-ID: <493615167.624945.1792405461616.JavaMail.zimbra@couthit.local> (raw)
In-Reply-To: <179214979438.408196.11375100740673315884@kernel.org>


Hi,
 
> This is an automated message. This series looks like a fix, but its
> commit messages seem to be missing some information:
> 
> - How the issue was discovered, e.g. hit in production, hit during
>   development, syzbot report, manual code inspection, LLM or static
>   analysis tool scan.
> 

Sashiko, the netdev AI review bot, reported it as a preexisting issue,
while reviewing our ICSSM HSR/PRP offload series
(https://lore.kernel.org/all/179151741150.434549.7819199497598747618@kernel.org).

> - Whether the issue was actually triggered, or is only theoretical
>   (e.g. found by code inspection). If it was triggered please include
>   the symptoms, like the stack trace or error messages.
> 

We first confirmed the issue by manual code review. We were also able to
replicate it on TI AM57xx IDK hardware board.

> - What hardware the change was tested on. For driver fixes please
>   mention the device (and if relevant firmware version) used for
>   testing, or say that the change was not tested on real hardware.
> 

We tested the fix on TI AM335x ICE / AM437x IDK / AM57xx IDK with the ICSS-M
PRUETH while changing the protocol from dual-EMAC to RSTP switch mode.


Thanks and Regards,
Sai Varun M.

  reply	other threads:[~2026-10-19 10:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 10:51 [PATCH net-next] net: ti: icssm-prueth: use dev_close()/dev_open() in icssm_prueth_change_mode() Sai Varun Mudepally
2026-10-16 11:23 ` netdev-bot+sinfo
2026-10-19 10:24   ` Saivarun Mudepally [this message]
2026-10-20 13:17 ` netdev-bot+sashiko

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=493615167.624945.1792405461616.JavaMail.zimbra@couthit.local \
    --to=saivarun@couthit.com \
    --cc=afd@ti.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=basharath@couthit.com \
    --cc=danishanwar@ti.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=j-rameshbabu@ti.com \
    --cc=krishna@couthit.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-malladi@ti.com \
    --cc=mohan@couthit.com \
    --cc=netdev-bot+sinfo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=parvathi@couthit.com \
    --cc=pmohan@couthit.com \
    --cc=praneeth@ti.com \
    --cc=pratheesh@ti.com \
    --cc=rogerq@kernel.org \
    --cc=rogerq@ti.com \
    --cc=srk@ti.com \
    --cc=vigneshr@ti.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.