From: Jakub Kicinski <kuba@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
loic.poulain@linaro.org
Subject: Re: [PATCH v2 0/2] Add MHI Endpoint network driver
Date: Mon, 27 Nov 2023 08:46:39 -0800 [thread overview]
Message-ID: <20231127084639.6be47207@kernel.org> (raw)
In-Reply-To: <20231127060439.GA2505@thinkpad>
On Mon, 27 Nov 2023 11:34:39 +0530 Manivannan Sadhasivam wrote:
> I think you made up your mind that this driver is exposing the network interface
> to the firmware on the device. I ought to clearify that the device running this
> driver doesn't necessarily be a modem but a PCIe endpoint instance that uses the
> netdev exposed by this driver to share data connectivity with another device.
Doesn't matter how many legit use cases you can come up with.
Using netdev as a device comm channel is something I am
fundamentally opposed to.
> This concept is not new and being supported by other protocols such as Virtio
> etc...
Yes. Use virtio, please.
next prev parent reply other threads:[~2023-11-27 16:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 15:24 [PATCH v2 0/2] Add MHI Endpoint network driver Manivannan Sadhasivam
2023-06-07 15:24 ` [PATCH v2 1/2] net: " Manivannan Sadhasivam
2023-06-07 16:27 ` Jeffrey Hugo
2023-06-07 16:52 ` Jeffrey Hugo
2023-06-07 17:39 ` Manivannan Sadhasivam
2023-06-07 17:16 ` Manivannan Sadhasivam
2023-06-07 17:08 ` Christophe JAILLET
2023-06-07 15:24 ` [PATCH v2 2/2] MAINTAINERS: Add entry for MHI networking drivers under MHI bus Manivannan Sadhasivam
2023-06-07 16:29 ` Jeffrey Hugo
2023-06-07 16:49 ` [PATCH v2 0/2] Add MHI Endpoint network driver Jakub Kicinski
2023-06-07 17:11 ` Manivannan Sadhasivam
2023-06-07 17:43 ` Jakub Kicinski
2023-06-08 12:37 ` Manivannan Sadhasivam
2023-11-17 7:06 ` Manivannan Sadhasivam
2023-11-18 0:26 ` Jakub Kicinski
2023-11-27 6:04 ` Manivannan Sadhasivam
2023-11-27 16:46 ` Jakub Kicinski [this message]
2023-11-28 20:35 ` Dmitry Baryshkov
2023-11-28 20:58 ` Jakub Kicinski
2023-12-04 12:12 ` Dmitry Baryshkov
2023-12-04 16:12 ` Jakub Kicinski
2023-12-05 14:22 ` Dmitry Baryshkov
2023-06-07 18:13 ` Andrew Lunn
2023-06-08 12:40 ` 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=20231127084639.6be47207@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mhi@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.