Dear developers,

I have met some issues about QMI CID leaks when using Quectel's modem with 
modem manager, and luckily I found some comments about the exactly some issue 
on the Mail Archive.(Re: QMI CID leaks 
(mail-archive.com)<https://www.mail-archive.com/modemmanager-devel@lists.freedesktop.org/msg05789.html>

In this post, it is said that "it looks like this could be fixed most easily in 
qmi-proxy. I will post a patch candidate for review/merging to libqmi project 
soon..." But we have investigated the latest version of MM, it seems that this 
issue remained unfixed.

So I wonder whether this issue have been fixed by your team. If it is, can you 
please share with us the correct version to use(maybe we have used the wrong 
version). Or do you have any suggestion to solve this issue? We will appreciate 
a lot if you can kindly share with us.

Hope this would't cause you too much inconvenience. Thanks a lot!

BR



________________________________



IOEE Jimmy Li | Specialist, Next Generation Cube Program

ioee.jimmy...@schindler.com<mailto:ioee.jimmy...@schindler.com>

迅达(中国)电梯有限公司 | IOEE
上海市嘉定区兴顺路555号
上海,201815,中国

www.schindler.com.cn<http://www.schindler.com.cn>

We Elevate

<https://www.youtube.com/schindlergroup>

<https://www.linkedin.com/company/schindler-group>

<https://www.schindler.com/cn/internet/en/mobility-solutions/products/escalators.html>

________________________________


*****************************************************************
The information contained in this message is intended only for use of the 
individual(s) named above and may contain confidential, proprietary or legally 
privileged information. No confidentiality or privilege is waived or lost by 
any mistransmission. If you are not the intended recipient of this message you 
are hereby notified that you must not use, disseminate, copy it in any form or 
take any action in reliance of it. If you have received this message in error 
please delete it and any copies of it and notify the sender immediately.
*****************************************************************

Reply via email to