From: <Parthiban.Veerasooran@microchip.com>
To: <Selvamani.Rajagopal@onsemi.com>, <andrew@lunn.ch>, <conor@kernel.org>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<Pier.Beruto@onsemi.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <Conor.Dooley@microchip.com>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH net v3 2/2] dt-bindings: net: updated interrupt type to be active low, level triggered
Date: Thu, 11 Jun 2026 13:01:08 +0000 [thread overview]
Message-ID: <56e6c9ea-2e2a-406d-b7d0-ec484e3170e6@microchip.com> (raw)
In-Reply-To: <CY8PR02MB9249B913E28E285EB46EC59C831D2@CY8PR02MB9249.namprd02.prod.outlook.com>
Hi Selvamani,
On 10/06/26 1:32 am, Selvamani Rajagopal wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
>> Subject: RE: [PATCH net v3 2/2] dt-bindings: net: updated interrupt type to be active low,
>> level triggered
>>
>>
>> Thanks Parthiban.
>> Though code was ready, I got into other things for the past two days. Please share your
>> changes. I will compare with mine before submitting.
>
>
> Parthiban,
>
> Just submitted the patches. When you have time, please review and test.
> As you could see, one change led to more investigation. I saw a traffic stall
> when I oversubscribed the traffic. That investigation led to extra patches.
>
> https://patchwork.kernel.org/project/netdevbpf/list/?series=1108804
Thank you for the update. I will test your v4 submission and share the
feedback as soon as possible.
Best regards,
Parthiban V
>
>
>>
>>>
>>> Best regards,
>>> Parthiban V
>>>>
>
next prev parent reply other threads:[~2026-06-11 13:01 UTC|newest]
Thread overview: 24+ 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-09 15:40 ` Selvamani Rajagopal
2026-06-09 20:02 ` Selvamani Rajagopal
2026-06-11 13:01 ` Parthiban.Veerasooran [this message]
2026-06-11 14:22 ` Selvamani Rajagopal
2026-06-11 21:59 ` Selvamani Rajagopal
2026-06-12 12:43 ` Parthiban.Veerasooran
2026-06-04 13:19 ` [PATCH net v3 0/2] Resubmitting with cover-letter and threaded patch series Paolo Abeni
2026-06-04 14:51 ` 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=56e6c9ea-2e2a-406d-b7d0-ec484e3170e6@microchip.com \
--to=parthiban.veerasooran@microchip.com \
--cc=Conor.Dooley@microchip.com \
--cc=Pier.Beruto@onsemi.com \
--cc=Selvamani.Rajagopal@onsemi.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--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=pabeni@redhat.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