From: Selvamani Rajagopal <Selvamani.Rajagopal@onsemi.com>
To: Parthiban Veerasooran <parthiban.veerasooran@microchip.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Lunn <andrew@lunn.ch>, Andrew Lunn <andrew+netdev@lunn.ch>,
Piergiorgio Beruto <Pier.Beruto@onsemi.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: RE: [PATCH net v4 2/3] net: ethernet: oa_tc6: Improvements to error recovery
Date: Mon, 27 Jul 2026 00:06:44 +0000 [thread overview]
Message-ID: <DM5PR02MB3369F0D8574CD2D41FD5462483CC2@DM5PR02MB3369.namprd02.prod.outlook.com> (raw)
In-Reply-To: <419bb6ee-297c-4b88-8306-bc6a286c2e54@microchip.com>
> -----Original Message-----
> From: Parthiban Veerasooran <parthiban.veerasooran@microchip.com>
> Sent: Wednesday, July 22, 2026 3:09 AM
>
> Imperative mood for the subject: "Improve error recovery" (netdev
> convention).
Done
>
> On 21/07/26 7:50 am, Selvamani Rajagopal via B4 Relay wrote:
> > size = end_byte_offset + 1;
> > oa_tc6_prcs_rx_frame_end(tc6, data, size);
> oa_tc6_prcs_rx_frame_end() now returns int, but this drops the return —
> every other call in this patch propagates it. Is it deliberate?
Yes. We are not checking the return code on purpose. (Indirect) Answer is in the
comment below. I will change the comment to mention this specifically for clarity.
> > +
> > + /* Purpose of rx_buf_overflow is make the
> > + * code to look for new frame. At this
> > + * stage, we have a new frame to process.
> > + * So, making it false, in case it is set
> > + * to true by oa_tc6_prcs_rx_frame_end.
> > + */
> > - return 0;
> > + return oa_tc6_prcs_ongoing_rx_frame(tc6, data, footer);
> footer is unused here. Either drop the unused parameter or a note why it
> stays.
I was surprised too as I don't remember adding it. When I checked, It was there before.
>
> Best regards,
> Parthiban V
> > }
> >
next prev parent reply other threads:[~2026-07-27 0:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 2:20 [PATCH net v4 0/3] Fix to possible skb leak due to race condtion in tx path Selvamani Rajagopal via B4 Relay
2026-07-21 2:20 ` [PATCH net v4 1/3] net: ethernet: oa_tc6: Protect skb pointer used by two different kernel instances Selvamani Rajagopal via B4 Relay
2026-07-22 10:08 ` Parthiban Veerasooran
2026-07-27 0:26 ` Selvamani Rajagopal
2026-07-21 2:20 ` [PATCH net v4 2/3] net: ethernet: oa_tc6: Improvements to error recovery Selvamani Rajagopal via B4 Relay
2026-07-22 10:09 ` Parthiban Veerasooran
2026-07-27 0:06 ` Selvamani Rajagopal [this message]
2026-07-21 2:20 ` [PATCH net v4 3/3] net: ethernet: oa_tc6: Disabled tx queues when disable_traffic is set Selvamani Rajagopal via B4 Relay
2026-07-22 10:09 ` Parthiban Veerasooran
2026-07-26 22:59 ` 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=DM5PR02MB3369F0D8574CD2D41FD5462483CC2@DM5PR02MB3369.namprd02.prod.outlook.com \
--to=selvamani.rajagopal@onsemi.com \
--cc=Pier.Beruto@onsemi.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parthiban.veerasooran@microchip.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®