linux-kernel - Re: [PATCH v4 3/3] net: wwan: mhi: make default data link id configurable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240701142826.25ccb798@kernel.org>
Date: Mon, 1 Jul 2024 14:28:26 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Slark Xiao <slark_xiao@....com>
Cc: manivannan.sadhasivam@...aro.org, loic.poulain@...aro.org,
 ryazanov.s.a@...il.com, johannes@...solutions.net, quic_jhugo@...cinc.com,
 netdev@...r.kernel.org, mhi@...ts.linux.dev, linux-arm-msm@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 3/3] net: wwan: mhi: make default data link id
 configurable

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@...nel.org>