[PATCH] device: avoid signals sent to the mbim-proxy process

Eric Caruso ejcaruso at chromium.org
Mon Aug 7 16:22:18 UTC 2017


> On Sun, 2017-08-06 at 13:13 +0200, Aleksander Morgado wrote:
>> What do you guys think? I believe this is reasonable, the proxy
>> should really be a complete independent spawn not tied to the process
>> which originated it.

For Chrome OS I was exploring spawning the mbim-proxy using a separate
upstart job to ensure this would be the case. This seems reasonable as
well.


More information about the libmbim-devel mailing list