From: Jakub Kicinski <kuba@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
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, 4 Dec 2023 08:12:22 -0800 [thread overview]
Message-ID: <20231204081222.31bb980a@kernel.org> (raw)
In-Reply-To: <CAA8EJpqGAK-7be1v8VktFRPpBHhUTwKJ=6JTTrFaWh341JAQEQ@mail.gmail.com>
On Mon, 4 Dec 2023 14:12:12 +0200 Dmitry Baryshkov wrote:
> Ok, here you are talking about the control path. I can then assume
> that you consider it to be fine to use netdev for the EP data path, if
> the control path is kept separate and those two can not be mixed. Does
> that sound correct?
If datapath == traffic which is intended to leave the card via
the external port, then yes.
next prev parent reply other threads:[~2023-12-04 16:12 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
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 [this message]
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=20231204081222.31bb980a@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dmitry.baryshkov@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).