From: Daniele Palmas <dnlplm@gmail.com>
To: "Bjørn Mork" <bjorn@mork.no>,
"David S . Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org,
Aleksander Morgado <aleksander@aleksander.es>,
Daniele Palmas <dnlplm@gmail.com>
Subject: [PATCH 0/2] net: usb: qmi_wwan: new mux_id sysfs file
Date: Mon, 25 Jan 2021 16:22:33 +0100 [thread overview]
Message-ID: <20210125152235.2942-1-dnlplm@gmail.com> (raw)
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.
Thanks,
Daniele
Daniele Palmas (2):
net: usb: qmi_wwan: add qmap id sysfs file for qmimux interfaces
net: qmi_wwan: document qmap/mux_id sysfs file
Documentation/ABI/testing/sysfs-class-net-qmi | 10 +++++++
drivers/net/usb/qmi_wwan.c | 27 +++++++++++++++++++
2 files changed, 37 insertions(+)
--
2.17.1
next reply other threads:[~2021-01-26 20:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 15:22 Daniele Palmas [this message]
2021-01-25 15:22 ` [PATCH net-next 1/2] net: usb: qmi_wwan: add qmap id sysfs file for qmimux interfaces Daniele Palmas
2021-01-25 16:14 ` Bjørn Mork
2021-01-27 2:02 ` Jakub Kicinski
2021-01-27 7:26 ` Bjørn Mork
2021-01-29 2:00 ` Jakub Kicinski
2021-01-25 16:33 ` Aleksander Morgado
2021-01-27 7:58 ` Greg KH
2021-01-25 15:22 ` [PATCH net-next 2/2] net: qmi_wwan: document qmap/mux_id sysfs file Daniele Palmas
2021-01-25 16:14 ` Bjørn Mork
-- strict thread matches above, loose matches on Subject: below --
2021-01-27 15:34 [PATCH 0/2] net: usb: qmi_wwan: new mux_id " Daniele Palmas
2021-01-29 2:10 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210125152235.2942-1-dnlplm@gmail.com \
--to=dnlplm@gmail.com \
--cc=aleksander@aleksander.es \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).