From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: Alexander Aring <alex.aring@gmail.com>,
linux-wpan@vger.kernel.org,
"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>,
Guilhem Imberton <guilhem.imberton@qorvo.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH wpan-next v3 0/2] IEEE 802.15.4 PAN discovery handling
Date: Tue, 29 Nov 2022 15:47:47 +0100 [thread overview]
Message-ID: <20221129154747.572d4da7@xps-13> (raw)
In-Reply-To: <04f7bc30-618d-db22-4b8f-8753f60d26b9@datenfreihafen.org>
Hi Stefan,
stefan@datenfreihafen.org wrote on Tue, 29 Nov 2022 15:39:13 +0100:
> Hello.
>
> On 29.11.22 14:55, Miquel Raynal wrote:
> > Hello,
> >
> >>>> Just a resent of the v2, rebased <<<
> >
> > Last preparation step before the introduction of the scanning feature
> > (really): generic helpers to handle PAN discovery upon beacon
> > reception. We need to tell user space about the discoveries.
> >
> > In all the past, current and future submissions, David and Romuald from
> > Qorvo are credited in various ways (main author, co-author,
> > suggested-by) depending of the amount of rework that was involved on
> > each patch, reflecting as much as possible the open-source guidelines we
> > follow in the kernel. All this effort is made possible thanks to Qorvo
> > Inc which is pushing towards a featureful upstream WPAN support.
> >
> > Cheers,
> > Miquèl
> >
> > Changes in v3:
> > * Rebased on wpan-next/master.
> >
> > Changes in v2:
> > * Dropped all the logic around the knowledge of PANs: we forward all
> > beacons received to userspace and let the user decide whether or not
> > the coordinator is new or not.
> > * Changed the coordinator descriptor address member to a proper
> > structure (not a pointer).
> >
> > David Girault (1):
> > mac802154: Trace the registration of new PANs
> >
> > Miquel Raynal (1):
> > ieee802154: Advertize coordinators discovery
> >
> > include/net/cfg802154.h | 18 +++++++
> > include/net/nl802154.h | 43 ++++++++++++++++
> > net/ieee802154/nl802154.c | 103 ++++++++++++++++++++++++++++++++++++++
> > net/ieee802154/nl802154.h | 2 +
> > net/mac802154/trace.h | 25 +++++++++
> > 5 files changed, 191 insertions(+)
> >
>
> These patches have been applied to the wpan-next tree and will be
> part of the next pull request to net-next. Thanks!
Perfect, thanks for your responsiveness!
Next series with proper passive scan support is coming.
Thanks,
Miquèl
prev parent reply other threads:[~2022-11-29 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 13:55 [PATCH wpan-next v3 0/2] IEEE 802.15.4 PAN discovery handling Miquel Raynal
2022-11-29 13:55 ` [PATCH wpan-next v3 1/2] ieee802154: Advertize coordinators discovery Miquel Raynal
2022-11-29 13:55 ` [PATCH wpan-next v3 2/2] mac802154: Trace the registration of new PANs Miquel Raynal
2022-11-29 14:39 ` [PATCH wpan-next v3 0/2] IEEE 802.15.4 PAN discovery handling Stefan Schmidt
2022-11-29 14:47 ` Miquel Raynal [this message]
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=20221129154747.572d4da7@xps-13 \
--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=guilhem.imberton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox