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>,
Guilhem Imberton <guilhem.imberton@qorvo.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH wpan 0/6] ieee802154: Scan/Beacon fixes
Date: Tue, 14 Feb 2023 14:39:04 +0100 [thread overview]
Message-ID: <20230214143904.2a9eebb6@xps-13> (raw)
In-Reply-To: <20230213165414.1168401-1-miquel.raynal@bootlin.com>
Hi all,
miquel.raynal@bootlin.com wrote on Mon, 13 Feb 2023 17:54:08 +0100:
> Hello,
>
> Following Jakub's review on Stefan's MR, a number of changes were
> requested for him in order to pull the patches in net. In the mean time,
> a couple of discussions happened with Alexander (return codes for
> monitor scans and transmit helper used for beacons).
>
> Hopefully this series addresses everything.
Looks like my 'Fixes' commit hash lookups lead to local tree hits rather
than matching the ones in the wpan-next tree, so these hashes won't
point at any valid commit once in the upstream trees. I am sending a v2
with nothing else than these commit hashes fixed.
Sorry for the noise.
Thanks,
Miquèl
>
> Thanks,
> Miquèl
>
> Miquel Raynal (6):
> ieee802154: Use netlink policies when relevant on scan parameters
> ieee802154: Convert scan error messages to extack
> ieee802154: Change error code on monitor scan netlink request
> mac802154: Send beacons using the MLME Tx path
> mac802154: Fix an always true condition
> ieee802154: Drop device trackers
>
> net/ieee802154/nl802154.c | 125 ++++++++++++++------------------------
> net/mac802154/scan.c | 25 ++++++--
> 2 files changed, 65 insertions(+), 85 deletions(-)
>
prev parent reply other threads:[~2023-02-14 13:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 16:54 [PATCH wpan 0/6] ieee802154: Scan/Beacon fixes Miquel Raynal
2023-02-13 16:54 ` [PATCH wpan 1/6] ieee802154: Use netlink policies when relevant on scan parameters Miquel Raynal
2023-02-13 16:54 ` [PATCH wpan 2/6] ieee802154: Convert scan error messages to extack Miquel Raynal
2023-02-13 16:54 ` [PATCH wpan 3/6] ieee802154: Change error code on monitor scan netlink request Miquel Raynal
2023-02-13 16:54 ` [PATCH wpan 4/6] mac802154: Send beacons using the MLME Tx path Miquel Raynal
2023-02-13 16:54 ` [PATCH wpan 5/6] mac802154: Fix an always true condition Miquel Raynal
2023-02-13 16:54 ` [PATCH wpan 6/6] ieee802154: Drop device trackers Miquel Raynal
2023-02-14 13:39 ` 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=20230214143904.2a9eebb6@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).