From: Jakub Kicinski <kuba@kernel.org>
To: Vivek Pernamitta <vivek.pernamitta@oss.qualcomm.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Manivannan Sadhasivam <mani@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v6 1/2] net: mhi: Enable Ethernet interface support
Date: Wed, 10 Dec 2025 18:38:27 +0900 [thread overview]
Message-ID: <20251210183827.7024a8cf@kernel.org> (raw)
In-Reply-To: <20251209-vdev_next-20251208_eth_v6-v6-1-80898204f5d8@quicinc.com>
On Tue, 09 Dec 2025 16:55:38 +0530 Vivek Pernamitta wrote:
> Add support to configure a new client as Ethernet type over MHI by
> setting "mhi_device_info.ethernet_if = true". Create a new Ethernet
> interface named eth%d. This complements existing NET driver support.
>
> Introduce IP_SW1, ETH0, and ETH1 network interfaces required for
> M-plane, NETCONF, and S-plane components.
>
> M-plane:
> Implement DU M-Plane software for non-real-time O-RAN management
> between O-DU and O-RU using NETCONF/YANG and O-RAN WG4 M-Plane YANG
> models. Provide capability exchange, configuration management,
> performance monitoring, and fault management per O-RAN.WG4.TS.MP.0-
> R004-v18.00.
Noob question perhaps, what does any of this have to do with Ethernet?
You need Ethernet to exchange NETCONF messages?
next prev parent reply other threads:[~2025-12-10 9:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 11:25 [PATCH v6 0/2] net: mhi: Add support to enable ethernet interface Vivek Pernamitta
2025-12-09 11:25 ` [PATCH v6 1/2] net: mhi: Enable Ethernet interface support Vivek Pernamitta
2025-12-09 13:36 ` Andrew Lunn
2025-12-10 6:30 ` vivek pernamitta
[not found] ` <eaf79686-9fcb-4330-8017-83a4e4923985@oss.qualcomm.com>
2025-12-10 16:50 ` Andrew Lunn
2025-12-22 10:31 ` vivek pernamitta
2025-12-10 9:38 ` Jakub Kicinski [this message]
2025-12-22 10:43 ` vivek pernamitta
2025-12-24 6:08 ` Manivannan Sadhasivam
2025-12-09 11:25 ` [PATCH v6 2/2] bus: mhi: host: pci: Enable IP_SW1, IP_ETH0 and IP_ETH1 channels for QDU100 Vivek Pernamitta
2025-12-10 9:39 ` Jakub Kicinski
2025-12-22 10:34 ` vivek pernamitta
2025-12-24 6:03 ` [PATCH v6 0/2] net: mhi: Add support to enable ethernet interface Manivannan Sadhasivam
2026-02-04 5:03 ` vivek pernamitta
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=20251210183827.7024a8cf@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vivek.pernamitta@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.