mbox series

[wpan-next,v2,0/2] IEEE 802.15.4 PAN discovery handling

Message ID 20221118221041.1402445-1-miquel.raynal@bootlin.com (mailing list archive)
Headers show
Series IEEE 802.15.4 PAN discovery handling | expand

Message

Miquel Raynal Nov. 18, 2022, 10:10 p.m. UTC
Hello,

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 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(+)

Comments

Alexander Aring Nov. 28, 2022, 10:11 p.m. UTC | #1
Hi,

On Fri, Nov 18, 2022 at 5:13 PM Miquel Raynal <miquel.raynal@bootlin.com> wrote:
>
> Hello,
>
> 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.
>

Acked-by: Alexander Aring <aahringo@redhat.com>

I am sorry, I saw this series today. Somehow I mess up my mails if we
are still writing something on v1 but v2 is already submitted. I will
try to keep up next time.

- Alex
Miquel Raynal Nov. 29, 2022, 8:03 a.m. UTC | #2
Hi Alexander,

aahringo@redhat.com wrote on Mon, 28 Nov 2022 17:11:38 -0500:

> Hi,
> 
> On Fri, Nov 18, 2022 at 5:13 PM Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> >
> > Hello,
> >
> > 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.
> >  
> 
> Acked-by: Alexander Aring <aahringo@redhat.com>
> 
> I am sorry, I saw this series today. Somehow I mess up my mails if we
> are still writing something on v1 but v2 is already submitted. I will
> try to keep up next time.

Haha I was asking myself wether or not you saw it, no problem :) I did
send it after your main review but we continued discussing on v1 (about
the preambles) so I did not ping for the time the discussion would
settle.

I'll continued with the scan interface which I think is the next step!

Thanks,
Miquèl
Stefan Schmidt Nov. 29, 2022, 12:41 p.m. UTC | #3
Hello.

On 29.11.22 09:03, Miquel Raynal wrote:
> Hi Alexander,
> 
> aahringo@redhat.com wrote on Mon, 28 Nov 2022 17:11:38 -0500:
> 
>> Hi,
>>
>> On Fri, Nov 18, 2022 at 5:13 PM Miquel Raynal <miquel.raynal@bootlin.com> wrote:
>>>
>>> Hello,
>>>
>>> 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.
>>>   
>>
>> Acked-by: Alexander Aring <aahringo@redhat.com>
>>
>> I am sorry, I saw this series today. Somehow I mess up my mails if we
>> are still writing something on v1 but v2 is already submitted. I will
>> try to keep up next time.
> 
> Haha I was asking myself wether or not you saw it, no problem :) I did
> send it after your main review but we continued discussing on v1 (about
> the preambles) so I did not ping for the time the discussion would
> settle.

I was trying to apply these two patches, but the first one does not apply:


Failed to apply patch:
error: patch failed: include/net/nl802154.h:58
error: include/net/nl802154.h: patch does not apply
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Applying: ieee802154: Advertize coordinators discovery
Patch failed at 0001 ieee802154: Advertize coordinators discovery

It seems you need a rebase as there is commit 
8254393663f9b8cb8b84cdce1abb118833c22a54 which touches this area of the 
file and removes a comment and ifdef. Should be fine to go in after the 
rebase.

regards
Stefan Schmidt
Miquel Raynal Nov. 29, 2022, 1:11 p.m. UTC | #4
Hi Stefan,

stefan@datenfreihafen.org wrote on Tue, 29 Nov 2022 13:41:32 +0100:

> Hello.
> 
> On 29.11.22 09:03, Miquel Raynal wrote:
> > Hi Alexander,
> > 
> > aahringo@redhat.com wrote on Mon, 28 Nov 2022 17:11:38 -0500:
> >   
> >> Hi,
> >>
> >> On Fri, Nov 18, 2022 at 5:13 PM Miquel Raynal <miquel.raynal@bootlin.com> wrote:  
> >>>
> >>> Hello,
> >>>
> >>> 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.  
> >>>   >>  
> >> Acked-by: Alexander Aring <aahringo@redhat.com>
> >>
> >> I am sorry, I saw this series today. Somehow I mess up my mails if we
> >> are still writing something on v1 but v2 is already submitted. I will
> >> try to keep up next time.  
> > 
> > Haha I was asking myself wether or not you saw it, no problem :) I did
> > send it after your main review but we continued discussing on v1 (about
> > the preambles) so I did not ping for the time the discussion would
> > settle.  
> 
> I was trying to apply these two patches, but the first one does not apply:
> 
> 
> Failed to apply patch:
> error: patch failed: include/net/nl802154.h:58
> error: include/net/nl802154.h: patch does not apply
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> Applying: ieee802154: Advertize coordinators discovery
> Patch failed at 0001 ieee802154: Advertize coordinators discovery
> 
> It seems you need a rebase as there is commit 8254393663f9b8cb8b84cdce1abb118833c22a54 which touches this area of the file and removes a comment and ifdef. Should be fine to go in after the rebase.

Oh crap, this is gonna conflict with a dozen of my patches /o\. Not hard
to solve though. Let me fix this by moving all new commands in this
header above the security commands.

I'll also have to update the wpan tools to use the same commands.

Thanks,
Miquèl