netdev - Re: [PATCH V2 07/16] net: iosm: mbim control device

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]

Date:   Thu, 6 May 2021 11:25:45 +0200
From:   Loic Poulain <loic.poulain@...aro.org>
To:     M Chetan Kumar <m.chetan.kumar@...el.com>
Cc:     Network Development <netdev@...r.kernel.org>,
        linux-wireless@...r.kernel.org, johannes@...solutions.net,
        krishna.c.sudi@...el.com, linuxwwan@...el.com
Subject: Re: [PATCH V2 07/16] net: iosm: mbim control device

Hi Chetan,

On Tue, 20 Apr 2021 at 18:14, M Chetan Kumar <m.chetan.kumar@...el.com> wrote:
>
> Implements a char device for MBIM protocol communication &
> provides a simple IOCTL for max transfer buffer size
> configuration.
>
> Signed-off-by: M Chetan Kumar <m.chetan.kumar@...el.com>

Now that the initial wwan framework support landed, could you migrate
to it for creating the MBIM 'WWAN port' instead of creating yet
another char driver? I see you introduced an IOCTL for packet size, I
see no objection to add that in the wwan core.

Regards,
Loic