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 S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, 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>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [PATCH wpan-next v2 0/6] net: ieee802154: PAN management
Date: Fri, 17 Jun 2022 21:32:48 +0200 [thread overview]
Message-ID: <20220617193254.1275912-1-miquel.raynal@bootlin.com> (raw)
Hello,
Last step before adding scan support, we need to introduce a proper PAN
description (with its main properties) and PAN management helpers.
This series provides generic code to do simple operations on PANs and
PAN coordinators.
Thanks,
Miquèl
Changes in v2:
* The main change is related to the use of the COORD interface (instead
of dropping it). Most of the actual diff is in the following series.
David Girault (1):
net: ieee802154: Trace the registration of new PANs
Miquel Raynal (5):
net: ieee802154: Create a device type
net: ieee802154: Ensure only FFDs can become PAN coordinators
net: mac802154: Allow the creation of PAN coordinator interfaces
net: ieee802154: Add support for inter PAN management
net: ieee802154: Give the user to the PAN information
include/net/cfg802154.h | 31 +++++
include/net/nl802154.h | 57 ++++++++++
net/ieee802154/Makefile | 2 +-
net/ieee802154/core.c | 2 +
net/ieee802154/core.h | 33 ++++++
net/ieee802154/nl802154.c | 206 ++++++++++++++++++++++++++++++++-
net/ieee802154/pan.c | 234 ++++++++++++++++++++++++++++++++++++++
net/ieee802154/trace.h | 25 ++++
net/mac802154/iface.c | 14 ++-
net/mac802154/rx.c | 2 +-
10 files changed, 595 insertions(+), 11 deletions(-)
create mode 100644 net/ieee802154/pan.c
--
2.34.1
next reply other threads:[~2022-06-17 19:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 19:32 Miquel Raynal [this message]
2022-06-17 19:32 ` [PATCH wpan-next v2 1/6] net: ieee802154: Create a device type Miquel Raynal
2022-06-20 0:18 ` Alexander Aring
2022-06-20 9:26 ` Miquel Raynal
2022-06-21 2:00 ` Alexander Aring
2022-06-17 19:32 ` [PATCH wpan-next v2 2/6] net: ieee802154: Ensure only FFDs can become PAN coordinators Miquel Raynal
2022-06-20 0:24 ` Alexander Aring
2022-06-20 0:25 ` Alexander Aring
2022-06-20 9:28 ` Miquel Raynal
2022-06-21 2:03 ` Alexander Aring
2022-06-21 6:31 ` Miquel Raynal
2022-06-17 19:32 ` [PATCH wpan-next v2 3/6] net: mac802154: Allow the creation of PAN coordinator interfaces Miquel Raynal
2022-06-17 19:32 ` [PATCH wpan-next v2 4/6] net: ieee802154: Add support for inter PAN management Miquel Raynal
2022-06-17 19:32 ` [PATCH wpan-next v2 5/6] net: ieee802154: Give the user to the PAN information Miquel Raynal
2022-06-17 19:32 ` [PATCH wpan-next v2 6/6] net: ieee802154: Trace the registration of new PANs 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=20220617193254.1275912-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=david.girault@qorvo.com \
--cc=edumazet@google.com \
--cc=frederic.blain@qorvo.com \
--cc=kuba@kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nico@ni.fr.eu.org \
--cc=pabeni@redhat.com \
--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.