From: Paolo Abeni <pabeni@redhat.com>
To: Selvamani.Rajagopal@onsemi.com,
Parthiban Veerasooran <parthiban.veerasooran@microchip.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Piergiorgio Beruto <pier.beruto@onsemi.com>,
Andrew Lunn <andrew@lunn.ch>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH net v3 0/2] Resubmitting with cover-letter and threaded patch series.
Date: Thu, 4 Jun 2026 15:19:00 +0200 [thread overview]
Message-ID: <42052da1-2d33-4023-b383-482006fcb628@redhat.com> (raw)
In-Reply-To: <20260601-level-trigger-v3-0-da73e7010532@onsemi.com>
On 6/1/26 6:07 PM, Selvamani Rajagopal via B4 Relay wrote:
> According to OPEN Alliance 10BASE-T1x MAC-PHY Serial Interface
> specification, MAC-PHY interrupt is "active low, level triggered".
> The specification mentions about the conditions in which the IRQ
> is asserted and deasserted.
>
> Bug is inadvertently introduced by treating the IRQ in the OA TC6
> framework driver and in dt-binding YAML file as edge triggered.
>
> Changes are done in two files
> - OA TC6 framework Ethernet driver
> - YAML file for the vendor that already uses OA TC6 framework.
>
> Maintainer for this driver is already informed and aware of these
> changes. Testing for these changes was done in onsemi's setup and
> found to be working.
>
> Signed-off-by: Selvamani Rajagopal <Selvamani.Rajagopal@onsemi.com>
Note for future submissions: the cover letter subj must refer to the
series content, and not to changes from the previous revision.
/P
next prev parent reply other threads:[~2026-06-04 13:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 16:07 [PATCH net v3 0/2] Resubmitting with cover-letter and threaded patch series Selvamani Rajagopal via B4 Relay
2026-06-01 16:07 ` [PATCH net v3 1/2] net: ethernet: oa_tc6: Interrupt is active low, level triggered Selvamani Rajagopal via B4 Relay
2026-06-01 16:07 ` [PATCH net v3 2/2] dt-bindings: net: updated interrupt type to be " Selvamani Rajagopal via B4 Relay
2026-06-02 16:42 ` Conor Dooley
2026-06-02 17:36 ` Selvamani Rajagopal
2026-06-03 15:08 ` Conor Dooley
2026-06-04 6:29 ` Parthiban.Veerasooran
2026-06-04 7:08 ` Nicolai Buchwitz
2026-06-04 15:21 ` Selvamani Rajagopal
2026-06-04 16:36 ` Conor Dooley
2026-06-04 17:00 ` Andrew Lunn
2026-06-08 4:13 ` Parthiban.Veerasooran
2026-06-08 4:44 ` Selvamani Rajagopal
2026-06-08 7:15 ` Andrew Lunn
2026-06-08 15:04 ` Selvamani Rajagopal
2026-06-09 9:15 ` Parthiban.Veerasooran
2026-06-04 13:19 ` Paolo Abeni [this message]
2026-06-04 14:51 ` [PATCH net v3 0/2] Resubmitting with cover-letter and threaded patch series Selvamani Rajagopal
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=42052da1-2d33-4023-b383-482006fcb628@redhat.com \
--to=pabeni@redhat.com \
--cc=Selvamani.Rajagopal@onsemi.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=parthiban.veerasooran@microchip.com \
--cc=pier.beruto@onsemi.com \
--cc=robh@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