All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: Kalle Valo <kvalo@kernel.org>,
	Stefan Schmidt <stefan@datenfreihafen.org>,
	linux-wpan - ML <linux-wpan@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
	"linux-wireless@vger.kernel.org Wireless" 
	<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: Fri, 21 Jan 2022 09:31:04 +0100	[thread overview]
Message-ID: <20220121093104.73132c5d@xps13> (raw)
In-Reply-To: <CAB_54W5ORQ7Po3k3rjZMqxf8YfrDk6E_wKGgir9G31RVSDnyqw@mail.gmail.com>

Hi Alexander,

alex.aring@gmail.com wrote on Thu, 20 Jan 2022 18:31:58 -0500:

> Hi Kalle and Miquel,
> 
> On Thu, 20 Jan 2022 at 08:10, Kalle Valo <kvalo@kernel.org> wrote:
> >
> > 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 thought it would make sense to cc wireless as they have similar
> paradigms constructs (probably due the fact both are IEEE standards?).
> As well we took some ideas from wireless as base. Moreover we were
> talking about things which wireless already solved.
> I was hoping to get some feedback if somebody knows the right do's and
> don'ts of managing a wireless subsystem and I am pretty sure some
> 802.11 developers have more knowledge about it than some 802.15.4
> developers (including myself).
> 
> I apologise for this. Please Miquel drop wireless for your future patch-series.

Ok, no problem!
 
> Miquel please slow down the amount of patches. First sending the
> fixes, then new features in small series one by one. And with one by
> one I mean after they are applied.

Yes no problem, I didn't want to flood you, but I was eager to share
the new sync tx implementation that we discussed earlier this week,
which meant I also needed to share the two 'small' series in between.

Thanks,
Miquèl

      reply	other threads:[~2022-01-21  8:31 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
2022-01-20 23:31   ` Alexander Aring
2022-01-21  8:31     ` 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=20220121093104.73132c5d@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.