From: <Parthiban.Veerasooran@microchip.com>
To: <wahrenst@gmx.net>
Cc: <netdev@vger.kernel.org>
Subject: Re: TODOs in oa_tc6
Date: Fri, 17 Apr 2026 12:05:12 +0000 [thread overview]
Message-ID: <4b978687-20b0-4bbf-a5d3-3e6cc8f302d4@microchip.com> (raw)
In-Reply-To: <74f610a7-d9e1-41eb-ba1a-3d446a232769@gmx.net>
Hi Stefan,
On 14/04/26 11:48 pm, Stefan Wahren wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know
> the content is safe
>
> Hello Parthiban,
>
> thank you for upstreaming the lan865x driver.
>
> When do you plan to fix these open TODOs in ethernet/oa_tc6?
Thank you for your review and for pointing this out.
At the moment, we unfortunately don’t have concrete plans to address the
TODOs in ethernet/oa_tc6, as our team is currently committed to other
projects. That said, this work is in my backlog, and I do intend to come
back to it when bandwidth allows.
Sorry for the inconvenience, and thank you for your patience and
understanding.
Best regards,
Parthiban V
>
> Best regards
prev parent reply other threads:[~2026-04-17 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 18:18 TODOs in oa_tc6 Stefan Wahren
2026-04-17 12:05 ` 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=4b978687-20b0-4bbf-a5d3-3e6cc8f302d4@microchip.com \
--to=parthiban.veerasooran@microchip.com \
--cc=netdev@vger.kernel.org \
--cc=wahrenst@gmx.net \
/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