Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: Aleksman4o <aleksman4o@gmail.com>
To: iwd@lists.linux.dev
Cc: Aleks Man <aleksman4o@gmail.com>, prestwoj@gmail.com
Subject: Re: [PATCH v3 0/3] dbus: expose per-BSS RSN capabilities
Date: Tue, 28 Jul 2026 16:31:00 +0300	[thread overview]
Message-ID: <20260728133104.3369436-1-aleksman4o@gmail.com> (raw)
In-Reply-To: <cover.1784069194.git.aleksman4o@gmail.com>

From: Aleks Man <aleksman4o@gmail.com>

Hi James,

A gentle follow-up on this series, which has now been pending for two
weeks. All iwd CI checks passed. The corresponding NetworkManager MR is
currently blocked on the proposed iwd D-Bus API:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2464

Would you have time to review the API approach, or is there anything else
you would like changed or tested?

Thanks,
Aleks

  parent reply	other threads:[~2026-07-28 13:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11 20:07 [RFC] dbus: expose per-BSS security capabilities Алексей
2026-07-14 13:27 ` James Prestwood
2026-07-14 20:36   ` [PATCH 0/3] dbus: expose per-BSS RSN capabilities Алексей
2026-07-14 20:37     ` [PATCH 1/3] network: expose RSN capabilities on BSS Алексей
2026-07-14 20:38     ` [PATCH 2/3] doc: document BasicServiceSet RSN property Алексей
2026-07-14 20:39     ` [PATCH 3/3] auto-t: test " Алексей
2026-07-14 21:12   ` [PATCH v2 0/3] dbus: expose per-BSS RSN capabilities Aleksman4o
2026-07-14 21:12     ` [PATCH v2 1/3] network: expose RSN capabilities on BSS Aleksman4o
2026-07-14 21:12     ` [PATCH v2 2/3] doc: document BasicServiceSet RSN property Aleksman4o
2026-07-14 21:12     ` [PATCH v2 3/3] auto-t: test " Aleksman4o
2026-07-14 22:48     ` [PATCH v3 0/3] dbus: expose per-BSS RSN capabilities Aleksman4o
2026-07-14 22:48       ` [PATCH v3 1/3] network: expose RSN capabilities on BSS Aleksman4o
2026-07-14 22:48       ` [PATCH v3 2/3] doc: document BasicServiceSet RSN property Aleksman4o
2026-07-14 22:48       ` [PATCH v3 3/3] auto-t: test " Aleksman4o
2026-07-28 13:31       ` Aleksman4o [this message]
2026-07-28 13:40       ` [PATCH v3 0/3] dbus: expose per-BSS RSN capabilities James Prestwood
2026-07-28 15:46         ` [PATCH v4 0/5] " Aleksman4o
2026-07-28 15:46           ` [PATCH v4 1/5] network: expose RSN capabilities on BSS Aleksman4o
2026-07-28 15:46           ` [PATCH v4 2/5] doc: document BasicServiceSet RSN property Aleksman4o
2026-07-28 15:46           ` [PATCH v4 3/5] auto-t: test " Aleksman4o
2026-07-28 15:46           ` [PATCH v4 4/5] client: display " Aleksman4o
2026-07-28 15:46           ` [PATCH v4 5/5] client: widen BSS property value column Aleksman4o
2026-07-28 18:40           ` [PATCH v4 0/5] dbus: expose per-BSS RSN capabilities James Prestwood

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=20260728133104.3369436-1-aleksman4o@gmail.com \
    --to=aleksman4o@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@gmail.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