From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>,
linux-wpan@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-wireless@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>
Subject: Re: [wpan-next 0/4] ieee802154: General preparation to scan support
Date: Thu, 20 Jan 2022 15:28:13 +0100 [thread overview]
Message-ID: <20220120152813.32e4b288@xps13> (raw)
In-Reply-To: <87r192imcy.fsf@tynnyri.adurom.net>
Hi Kalle,
kvalo@kernel.org wrote on Thu, 20 Jan 2022 15:10:37 +0200:
> Miquel Raynal <miquel.raynal@bootlin.com> writes:
>
> > These few patches are preparation patches and light cleanups before the
> > introduction of scan support.
> >
> > David Girault (4):
> > net: ieee802154: Move IEEE 802.15.4 Kconfig main entry
> > net: mac802154: Include the softMAC stack inside the IEEE 802.15.4
> > menu
> > net: ieee802154: Move the address structure earlier
> > net: ieee802154: Add a kernel doc header to the ieee802154_addr
> > structure
> >
> > include/net/cfg802154.h | 28 +++++++++++++++++++---------
> > net/Kconfig | 3 +--
> > net/ieee802154/Kconfig | 1 +
> > 3 files changed, 21 insertions(+), 11 deletions(-)
>
> Is there a reason why you cc linux-wireless? It looks like there's a
> separate linux-wpan list now and people who are interested about wpan
> can join that list, right?
>
I originally was advised to cc linux-wireless@ on my scanning series,
and I ended up with too many patches, leading to numerous smaller
series.
I actually forgot to drop this list from the Cc list in the preparation
patches for this version, I did however dropped it in the v2. Sorry for
the noise.
Thanks,
Miquèl
next prev parent reply other threads:[~2022-01-20 14:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 0:43 [wpan-next 0/4] ieee802154: General preparation to scan support Miquel Raynal
2022-01-20 0:43 ` [wpan-next 1/4] net: ieee802154: Move IEEE 802.15.4 Kconfig main entry Miquel Raynal
2022-01-20 0:43 ` [wpan-next 2/4] net: mac802154: Include the softMAC stack inside the IEEE 802.15.4 menu Miquel Raynal
2022-01-27 16:04 ` Stefan Schmidt
2022-01-27 16:54 ` Miquel Raynal
2022-01-28 12:35 ` Stefan Schmidt
2022-01-28 14:04 ` Miquel Raynal
2022-01-30 20:55 ` Alexander Aring
2022-01-20 0:43 ` [wpan-next 3/4] net: ieee802154: Move the address structure earlier Miquel Raynal
2022-01-20 0:43 ` [wpan-next 4/4] net: ieee802154: Add a kernel doc header to the ieee802154_addr structure Miquel Raynal
2022-01-27 16:05 ` Stefan Schmidt
2022-01-27 16:51 ` Miquel Raynal
2022-01-20 13:10 ` [wpan-next 0/4] ieee802154: General preparation to scan support Kalle Valo
2022-01-20 14:28 ` Miquel Raynal [this message]
2022-01-20 23:31 ` Alexander Aring
2022-01-21 8:31 ` 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=20220120152813.32e4b288@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=david.girault@qorvo.com \
--cc=frederic.blain@qorvo.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nico@ni.fr.eu.org \
--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.