From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: Alexander Aring <aahringo@redhat.com>,
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 v2 0/2] IEEE 802.15.4 PAN discovery handling
Date: Tue, 29 Nov 2022 14:11:14 +0100 [thread overview]
Message-ID: <20221129141114.2b78240b@xps-13> (raw)
In-Reply-To: <ff0e20e9-687c-75f7-12ea-c927df39a1db@datenfreihafen.org>
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
prev parent reply other threads:[~2022-11-29 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 22:10 [PATCH wpan-next v2 0/2] IEEE 802.15.4 PAN discovery handling Miquel Raynal
2022-11-18 22:10 ` [PATCH wpan-next v2 1/2] ieee802154: Advertize coordinators discovery Miquel Raynal
2022-11-18 22:10 ` [PATCH wpan-next v2 2/2] mac802154: Trace the registration of new PANs Miquel Raynal
2022-11-28 22:11 ` [PATCH wpan-next v2 0/2] IEEE 802.15.4 PAN discovery handling Alexander Aring
2022-11-29 8:03 ` Miquel Raynal
2022-11-29 12:41 ` Stefan Schmidt
2022-11-29 13:11 ` 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=20221129141114.2b78240b@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=aahringo@redhat.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;
as well as URLs for NNTP newsgroup(s).