From: Jay Monkman <jtm@lopingdog.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: devicetree@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Piergiorgio Beruto <piergiorgio.beruto@gmail.com>,
Arndt Schuebel <Arndt.Schuebel@onsemi.com>,
Parthiban.Veerasooran@microchip.com
Subject: Re: [PATCH 4/4] net/onsemi: Add NCN26010 driver
Date: Mon, 18 Sep 2023 21:54:52 -0500 [thread overview]
Message-ID: <ZQkNfAOYgsBIhBRW@lopingdog.com> (raw)
In-Reply-To: <6e19020f-10ff-429b-8df3-cad5e5624e01@lunn.ch>
On Mon, Sep 18, 2023 at 06:00:37PM +0200, Andrew Lunn wrote:
> Is this an OA TC6 device? At a quick look it does appear to
> be. Please make use of the framework Microchip is developing:
>
> https://lore.kernel.org/netdev/20230908142919.14849-4-Parthiban.Veerasooran@microchip.com/T/
Yes it is. I wasn't aware of Microchip's work. Thanks for pointing it out.
next prev parent reply other threads:[~2023-09-19 2:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 6:59 [PATCH 4/4] net/onsemi: Add NCN26010 driver Jay Monkman
2023-09-18 16:00 ` Andrew Lunn
2023-09-19 2:54 ` Jay Monkman [this message]
2023-09-19 9:47 ` Paolo Abeni
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=ZQkNfAOYgsBIhBRW@lopingdog.com \
--to=jtm@lopingdog.com \
--cc=Arndt.Schuebel@onsemi.com \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=piergiorgio.beruto@gmail.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