From: Jakub Kicinski <kuba@kernel.org>
To: Slark Xiao <slark_xiao@163.com>
Cc: manivannan.sadhasivam@linaro.org, loic.poulain@linaro.org,
ryazanov.s.a@gmail.com, johannes@sipsolutions.net,
quic_jhugo@quicinc.com, netdev@vger.kernel.org,
mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/3] net: wwan: mhi: make default data link id configurable
Date: Mon, 1 Jul 2024 14:28:26 -0700 [thread overview]
Message-ID: <20240701142826.25ccb798@kernel.org> (raw)
In-Reply-To: <20240701021216.17734-3-slark_xiao@163.com>
On Mon, 1 Jul 2024 10:12:16 +0800 Slark Xiao wrote:
> For SDX72 MBIM mode, it starts data mux id from 112 instead of 0.
> This would lead to device can't ping outside successfully.
> Also MBIM side would report "bad packet session (112)". In order
> to fix this issue, we decide to use the device name of MHI
> controller to do a match in wwan side. Then wwan driver could
> set a corresponding mux_id value according to the MHI product.
Sounds like Mani wants to take these so:
Acked-by: Jakub Kicinski <kuba@kernel.org>
next prev parent reply other threads:[~2024-07-01 21:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 2:12 [PATCH v4 1/3] bus: mhi: host: Add Foxconn SDX72 related support Slark Xiao
2024-07-01 2:12 ` [PATCH v4 2/3] bus: mhi: host: Add name for mhi_controller Slark Xiao
2024-07-01 15:13 ` Jeffrey Hugo
2024-07-01 16:27 ` Manivannan Sadhasivam
2024-07-02 6:36 ` Slark Xiao
2024-07-03 13:46 ` Manivannan Sadhasivam
2024-07-01 2:12 ` [PATCH v4 3/3] net: wwan: mhi: make default data link id configurable Slark Xiao
2024-07-01 21:28 ` Jakub Kicinski [this message]
2024-07-03 13:46 ` Manivannan Sadhasivam
2024-07-01 16:25 ` [PATCH v4 1/3] bus: mhi: host: Add Foxconn SDX72 related support Manivannan Sadhasivam
2024-07-02 6:34 ` Slark Xiao
2024-07-03 13:28 ` Manivannan Sadhasivam
2024-07-03 13:44 ` 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=20240701142826.25ccb798@kernel.org \
--to=kuba@kernel.org \
--cc=johannes@sipsolutions.net \
--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=quic_jhugo@quicinc.com \
--cc=ryazanov.s.a@gmail.com \
--cc=slark_xiao@163.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).