From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>,
linux-wpan@vger.kernel.org
Cc: David Girault <david.girault@qorvo.com>,
Romuald Despres <romuald.despres@qorvo.com>,
Frederic Blain <frederic.blain@qorvo.com>,
Nicolas Schodet <nico@ni.fr.eu.org>,
Guilhem Imberton <guilhem.imberton@qorvo.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [PATCH wpan-tools v2 0/8] iwpan: Scan support
Date: Fri, 6 Jan 2023 12:18:23 +0100 [thread overview]
Message-ID: <20230106111831.692202-1-miquel.raynal@bootlin.com> (raw)
Hello,
This series follows the work done in the Linux kernel stack [1]: now
that the core knows about the different netlink commands and attributes
in order to support scanning requests, we can sync the userspace tools
to use them.
As part of these additions, a few cleanup patches are introducing the
series, including a first sync with a recent change in nl802154.h.
[1] https://lore.kernel.org/linux-wpan/ec93100f-8c55-2f54-d3d5-63f31c2602f4@datenfreihafen.org/T/#t
Cheers,
Miquèl
Changes in v2:
* Adapted to the latest kernel changes.
* Added a real "monitor" command in place of the scan done command.
* Renamed iwpan event into iwpan monitor.
* Dropped an unused function.
* Changed the behavior of the scan monitor call.
* Added SIGINT support to send an abort.
* Avoided a race in the scan command by using pthread when starting to
monitor, before triggering the scan operation.
* Dropped beaconing support for this first version.
David Girault (4):
iwpan: Export iwpan_debug
iwpan: Remove duplicated SECTION
iwpan: Add scan support
iwpan: Add events support
Miquel Raynal (3):
iwpan: Synchronize nl802154.h with the latest kernel
iwpan: Fix a comment
iwpan: Synchronize nl802154.h with the latest scan changes
Romuald Despres (1):
iwpan: Fix the channels printing
src/Makefile.am | 2 +
src/event.c | 230 ++++++++++++++++++++
src/info.c | 2 +-
src/iwpan.c | 2 +-
src/iwpan.h | 10 +-
src/nl802154.h | 107 +++++++++-
src/scan.c | 548 ++++++++++++++++++++++++++++++++++++++++++++++++
7 files changed, 888 insertions(+), 13 deletions(-)
create mode 100644 src/event.c
create mode 100644 src/scan.c
--
2.34.1
next reply other threads:[~2023-01-06 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 11:18 Miquel Raynal [this message]
2023-01-06 11:18 ` [PATCH wpan-tools v2 1/8] iwpan: Synchronize nl802154.h with the latest kernel Miquel Raynal
2023-01-06 11:18 ` [PATCH wpan-tools v2 2/8] iwpan: Fix the channels printing Miquel Raynal
2023-01-06 11:18 ` [PATCH wpan-tools v2 3/8] iwpan: Export iwpan_debug Miquel Raynal
2023-01-06 11:18 ` [PATCH wpan-tools v2 4/8] iwpan: Fix a comment Miquel Raynal
2023-01-06 11:18 ` [PATCH wpan-tools v2 5/8] iwpan: Remove duplicated SECTION Miquel Raynal
2023-01-06 11:18 ` [PATCH wpan-tools v2 6/8] iwpan: Synchronize nl802154.h with the latest scan changes Miquel Raynal
2023-01-06 11:18 ` [PATCH wpan-tools v2 7/8] iwpan: Add scan support Miquel Raynal
2023-01-06 11:18 ` [PATCH wpan-tools v2 8/8] iwpan: Add events support Miquel Raynal
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=20230106111831.692202-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=alex.aring@gmail.com \
--cc=david.girault@qorvo.com \
--cc=frederic.blain@qorvo.com \
--cc=guilhem.imberton@qorvo.com \
--cc=linux-wpan@vger.kernel.org \
--cc=nico@ni.fr.eu.org \
--cc=romuald.despres@qorvo.com \
--cc=stefan@datenfreihafen.org \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.