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]

Message-ID: <fd6b57f1e3b1444383ad5387de36e1cc@intel.com>
Date:   Thu, 6 May 2021 10:44:56 +0000
From:   "Kumar, M Chetan" <m.chetan.kumar@...el.com>
To:     Loic Poulain <loic.poulain@...aro.org>
CC:     Network Development <netdev@...r.kernel.org>,
        "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
        "johannes@...solutions.net" <johannes@...solutions.net>,
        "Sudi, Krishna C" <krishna.c.sudi@...el.com>,
        linuxwwan <linuxwwan@...el.com>
Subject: RE: [PATCH V2 07/16] net: iosm: mbim control device

Hi Loic,

> >
> > 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.
> 

Sure, we have started the migration to MBIM 'WWAN port'. The next version of patch
would contain these adaptations.

If wwan core supports IOCTL for packet size, then we shall remove that piece of
implementation in driver code.

Regards
Chetan