From: Jakub Kicinski <kuba@kernel.org>
To: Vivek.Pernamitta@quicinc.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>,
Vivek Pernamitta <quic_vpernami@quicinc.com>
Subject: Re: [PATCH 1/4] net: mhi: Rename MHI interface to improve clarity
Date: Fri, 25 Jul 2025 17:08:55 -0700 [thread overview]
Message-ID: <20250725170855.072f7011@kernel.org> (raw)
In-Reply-To: <20250724-b4-eth_us-v1-1-4dff04a9a128@quicinc.com>
On Thu, 24 Jul 2025 19:21:17 +0530 Vivek.Pernamitta@quicinc.com wrote:
> From: Vivek Pernamitta <quic_vpernami@quicinc.com>
>
> Rename the MHI network interface to include the device name, improving
> clarity when multiple MHI controllers are connected.
>
> Currently, MHI NET device interfaces are created as mhi_swip<n>/
> mhi_hwip<n> for each channel, making it difficult to distinguish between
> channels when multiple EP/MHI controllers are connected.
>
> Rename the MHI interface to include the device name, for example:
> - Channel IP_SW0 for the 1st MHI controller will be named mhi0_IP_SW0.
> - Channel IP_SW0 for the 2nd MHI controller will be named mhi1_IP_SW0.
> - Channel IP_HW0 for the 1st MHI controller will be named mhi0_IP_HW0.
The userspace can rename the interfaces. It has the association with
the underlying device right there in the udev event.
next prev parent reply other threads:[~2025-07-26 0:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 13:51 [PATCH 0/4] net: mhi : Add support to enable ethernet interface Vivek.Pernamitta
2025-07-24 13:51 ` [PATCH 1/4] net: mhi: Rename MHI interface to improve clarity Vivek.Pernamitta
2025-07-26 0:08 ` Jakub Kicinski [this message]
2025-07-24 13:51 ` [PATCH 2/4] net: mhi : Add support to enable ethernet interface Vivek.Pernamitta
2025-07-26 0:10 ` Jakub Kicinski
2025-07-24 13:51 ` [PATCH 3/4] net: mhi: Add MHI IP_SW1, ETH0 and ETH1 interface Vivek.Pernamitta
2025-07-24 13:51 ` [PATCH 4/4] bus: mhi: host: pci: Enable IP_SW1, IP_ETH0 and IP_ETH1 channels for QDU100 Vivek.Pernamitta
2025-07-24 16:39 ` [PATCH 0/4] net: mhi : Add support to enable ethernet interface Manivannan Sadhasivam
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=20250725170855.072f7011@kernel.org \
--to=kuba@kernel.org \
--cc=Vivek.Pernamitta@quicinc.com \
--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=quic_vpernami@quicinc.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