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] [day] [month] [year] [list]
Message-Id: 
 <174911942850.3016846.13970926519962437747.git-patchwork-notify@kernel.org>
Date: Thu, 05 Jun 2025 10:30:28 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Daniele Palmas <dnlplm@...il.com>
Cc: loic.poulain@....qualcomm.com, ryazanov.s.a@...il.com,
 johannes@...solutions.net, slark_xiao@....com,
 manivannan.sadhasivam@...aro.org, andrew+netdev@...n.ch, davem@...emloft.net,
 kuba@...nel.org, pabeni@...hat.com, edumazet@...gle.com,
 netdev@...r.kernel.org
Subject: Re: [PATCH net v2 1/1] net: wwan: mhi_wwan_mbim: use correct mux_id
 for
 multiplexing

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@...hat.com>:

On Tue,  3 Jun 2025 11:12:04 +0200 you wrote:
> Recent Qualcomm chipsets like SDX72/75 require MBIM sessionId mapping
> to muxId in the range (0x70-0x8F) for the PCIe tethered use.
> 
> This has been partially addressed by the referenced commit, mapping
> the default data call to muxId = 112, but the multiplexed data calls
> scenario was not properly considered, mapping sessionId = 1 to muxId
> 1, while it should have been 113.
> 
> [...]

Here is the summary with links:
  - [net,v2,1/1] net: wwan: mhi_wwan_mbim: use correct mux_id for multiplexing
    https://git.kernel.org/netdev/net/c/501fe52aa908

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ