Linux IEEE 802.15.4 and 6LoWPAN development
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Aring <aahringo@redhat.com>
Cc: Alexander Aring <alex.aring@gmail.com>,
	Stefan Schmidt <stefan@datenfreihafen.org>,
	linux-wpan@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/4] ieee802154: Active scan support
Date: Fri, 24 Mar 2023 10:57:37 +0100	[thread overview]
Message-ID: <20230324105737.0fb0f39f@xps-13> (raw)
In-Reply-To: <CAK-6q+iw6V5qDCux0E4xE3wMuCc1u8tc26kzwQFyHbMcyFr4iQ@mail.gmail.com>

Hi,

aahringo@redhat.com wrote on Thu, 23 Mar 2023 08:58:43 -0400:

> Hi,
> 
> On Fri, Mar 10, 2023 at 10:12 AM Miquel Raynal
> <miquel.raynal@bootlin.com> wrote:
> >
> > Hello,
> > Following the initial support for passive scan and beaconing, here is an
> > addition to support active scans.
> > Thanks,
> > Miquèl  
> 
> Acked-by: Alexander Aring <aahringo@redhat.com>
> 
> but I need to admit those are more scan mechanism related work and I
> trust Miquel he does the right thing, because he is actually more into
> this topic as me and worked previously on it.
> For me, I do not see anything that will break something e.g.
> overwriting framebuffer/dealing with frame filter levels and I am
> pretty sure Miquel already knows to take care of it.

I agree with the fact that the risk is rather low on this one. Now
coming:
- Handling of limited devices (ca8210)
- Associations/dis-associations (+ additional care to avoid confusing
  the devices)

> 
> Even if there would later be a problem regarding that, we can
> hopefully work things out.

Of course.

> 
> Thanks.
> 
> Sorry for the late reply.
> 
> - Alex
> 


Thanks!
Miquèl

  parent reply	other threads:[~2023-03-24  9:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 14:53 [PATCH wpan-next v2 0/4] ieee802154: Active scan support Miquel Raynal
2023-03-10 14:53 ` [PATCH wpan-next v2 1/4] ieee802154: Add support for user active scan requests Miquel Raynal
2023-03-10 14:53 ` [PATCH wpan-next v2 2/4] mac802154: Handle active scanning Miquel Raynal
2023-03-10 14:53 ` [PATCH wpan-next v2 3/4] ieee802154: Add support for allowing to answer BEACON_REQ Miquel Raynal
2023-03-10 14:53 ` [PATCH wpan-next v2 4/4] mac802154: Handle received BEACON_REQ Miquel Raynal
2023-03-23 12:58 ` [PATCH wpan-next v2 0/4] ieee802154: Active scan support Alexander Aring
2023-03-23 20:56   ` Stefan Schmidt
2023-03-24  9:57   ` Miquel Raynal [this message]
2023-03-24 12:27     ` Alexander Aring

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=20230324105737.0fb0f39f@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=aahringo@redhat.com \
    --cc=alex.aring@gmail.com \
    --cc=david.girault@qorvo.com \
    --cc=frederic.blain@qorvo.com \
    --cc=guilhem.imberton@qorvo.com \
    --cc=linux-wpan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox