From: Andrew Lunn <andrew@lunn.ch>
To: Potin Lai <potin.lai.pt@gmail.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Oliver Neukum <oliver@neukum.org>,
Samuel Mendoza-Jonas <sam@mendozajonas.com>,
Paul Fertser <fercerpav@gmail.com>,
Simon Horman <horms@kernel.org>,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Cosmo Chou <cosmo.chou@quantatw.com>,
Mike Hsieh <Mike_Hsieh@quantatw.com>,
Mik Lin <Mik.Lin@quantatw.com>,
Potin Lai <potin.lai@quantatw.com>,
Adrian Ambrozewicz <aambrozewicz@nvidia.com>
Subject: Re: [PATCH v2 1/2] net: usb: cdc_ether: add NCSI passthrough support
Date: Wed, 9 Sep 2026 20:47:47 +0200 [thread overview]
Message-ID: <f398b930-0049-44eb-a4c5-64a08befe76b@lunn.ch> (raw)
In-Reply-To: <20260908-ncsi-over-usb-v2-1-92dd78272fbd@gmail.com>
On Tue, Sep 08, 2026 at 09:01:31PM +0800, Potin Lai wrote:
> From: Adrian Ambrozewicz <aambrozewicz@nvidia.com>
>
You posted while there was still ongoing discussion.
> - Keep carrier always on while interface is up, as NCSI control traffic
> shares the USB data path (unlike PHY-based drivers)
> - Ignore CDC status notifications since NCSI manages link state
Why is the emulator send such notifications?
Andrew
---
pw-bot: cr
next prev parent reply other threads:[~2026-09-09 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 13:01 [PATCH v2 0/2] net: add USB CDC Ethernet NCSI support and fix unregister UAF Potin Lai
2026-09-08 13:01 ` [PATCH v2 1/2] net: usb: cdc_ether: add NCSI passthrough support Potin Lai
2026-09-09 18:47 ` Andrew Lunn [this message]
2026-09-08 13:01 ` [PATCH v2 2/2] net/ncsi: fix use-after-free in ncsi_unregister_dev() Potin Lai
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=f398b930-0049-44eb-a4c5-64a08befe76b@lunn.ch \
--to=andrew@lunn.ch \
--cc=Mik.Lin@quantatw.com \
--cc=Mike_Hsieh@quantatw.com \
--cc=aambrozewicz@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=cosmo.chou@quantatw.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fercerpav@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=pabeni@redhat.com \
--cc=potin.lai.pt@gmail.com \
--cc=potin.lai@quantatw.com \
--cc=sam@mendozajonas.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