Linux-WPAN Archive mirror
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
	Alexander Aring <alex.aring@gmail.com>,
	linux-wpan@vger.kernel.org
Cc: 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-tools 0/2] Associations support
Date: Thu, 7 Dec 2023 22:04:56 +0100	[thread overview]
Message-ID: <521b3a2b-70eb-0eb1-c2fd-76c0fe7e207a@datenfreihafen.org> (raw)
In-Reply-To: <20231128112945.509331-1-miquel.raynal@bootlin.com>

Hello.

On 28.11.23 12:29, Miquel Raynal wrote:
> Hello,
> 
> Associations will be part of the next kernel merge window, so here is
> the userspace part to interact with it.
> 
> Thanks,
> Miquèl
> 
> Miquel Raynal (2):
>    iwpan: Synchronize nl802154.h with the latest association changes
>    iwpan: Add associations support
> 
>   src/info.c     |   4 ++
>   src/mac.c      | 187 +++++++++++++++++++++++++++++++++++++++++++++++++
>   src/nl802154.h |  22 +++++-
>   3 files changed, 211 insertions(+), 2 deletions(-)
> 

I pushed both of thee now into the associations-support topic branch of 
wpan-tools. Once A kernel is released with the support we can merge it 
into the main branch.

regards
Stefan Schmidt

      parent reply	other threads:[~2023-12-07 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 11:29 [PATCH wpan-tools 0/2] Associations support Miquel Raynal
2023-11-28 11:29 ` [PATCH wpan-tools 1/2] iwpan: Synchronize nl802154.h with the latest association changes Miquel Raynal
2023-11-28 11:29 ` [PATCH wpan-tools 2/2] iwpan: Add associations support Miquel Raynal
2023-12-07 21:04 ` Stefan Schmidt [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=521b3a2b-70eb-0eb1-c2fd-76c0fe7e207a@datenfreihafen.org \
    --to=stefan@datenfreihafen.org \
    --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=miquel.raynal@bootlin.com \
    --cc=nico@ni.fr.eu.org \
    --cc=romuald.despres@qorvo.com \
    --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).