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] [day] [month] [year] [list]
Date:   Fri, 29 Jan 2021 02:10:11 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Daniele Palmas <dnlplm@...il.com>
Cc:     bjorn@...k.no, davem@...emloft.net, kuba@...nel.org,
        netdev@...r.kernel.org, linux-usb@...r.kernel.org,
        aleksander@...ksander.es
Subject: Re: [PATCH 0/2] net: usb: qmi_wwan: new mux_id sysfs file

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Wed, 27 Jan 2021 16:34:31 +0100 you wrote:
> Hello,
> 
> this patch series add a sysfs file to let userspace know which mux
> id has been used to create a qmimux network interface.
> 
> I'm aware that adding new sysfs files is not usually the right path,
> but my understanding is that this piece of information can't be
> retrieved in any other way and its absence restricts how
> userspace application (e.g. like libqmi) can take advantage of the
> qmimux implementation in qmi_wwan.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] net: usb: qmi_wwan: add qmap id sysfs file for qmimux interfaces
    https://git.kernel.org/netdev/net-next/c/e594ad980ec2
  - [net-next,v2,2/2] net: qmi_wwan: document qmap/mux_id sysfs file
    https://git.kernel.org/netdev/net-next/c/b4b91e24094a

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ