netdev - WWAN rtnetlink follow-up

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-next>] [day] [month] [year] [list]

Date:   Fri, 4 Jun 2021 12:27:56 +0200
From:   Loic Poulain <loic.poulain@...aro.org>
To:     M Chetan Kumar <m.chetan.kumar@...el.com>,
        Johannes Berg <johannes@...solutions.net>,
        Sergey Ryazanov <ryazanov.s.a@...il.com>
Cc:     Network Development <netdev@...r.kernel.org>,
        Jakub Kicinski <kuba@...nel.org>,
        David Miller <davem@...emloft.net>,
        Dan Williams <dcbw@...hat.com>
Subject: WWAN rtnetlink follow-up

Hi folks,

Thanks for your involvement and great work on this WWAN topic. I've
picked your patches in my tree for testing (with a Qualcomm MHI
modem):
https://git.linaro.org/people/loic.poulain/linux.git/log/?h=wwan-dev

This is minimal support for now since mhi_net only supports one link,
Essentially for testing purposes, but I plan to rework it to support
more than one once wwan rtnetlink is accepted and merged, This
limitation will not exist for the Intel IOSM driver.

I'm probably going to rebase that and squash the fix commits (from
Sergey and I) to Johannes changes if everyone agrees. Then I'll submit
the entire series.

Not sure what is the procedure for iproute2, should it be included in
the series or be part of a dedicated one?

Chetan, you can use that tree for your iosm work, or cherry-pick the
[FIXUP] changes if you already work on the submitted RFC series.

Refs:
https://lore.kernel.org/netdev/20210602082840.85828-1-johannes@xxxxxxxxxxxxxxxx/
https://lore.kernel.org/netdev/20210603044954.8091-1-ryazanov.s.a@gmail.com/

Thanks,
Loic