public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v2 4/8] station: emit property changed for ConnectedAccessPoint
Date: Fri, 23 Aug 2024 11:10:32 -0500	[thread overview]
Message-ID: <e8ed4323-4ec3-43d5-be0c-768596430911@gmail.com> (raw)
In-Reply-To: <20240819175151.1310546-4-prestwoj@gmail.com>

Hi James,

On 8/19/24 12:51 PM, James Prestwood wrote:
> This was missed in a prior patch set. When station is connecting
> or disconnecting ConnectedAccessPoint property change should be
> emitted.
> ---
>   src/station.c | 4 ++++
>   1 file changed, 4 insertions(+)

Applied, thanks.

Regards,
-Denis


  reply	other threads:[~2024-08-23 16:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19 17:51 [PATCH v2 1/8] doc: Document station Affinities property James Prestwood
2024-08-19 17:51 ` [PATCH v2 2/8] netdev: store signal threshold in netdev object, not globally James Prestwood
2024-08-19 17:51 ` [PATCH v2 3/8] netdev: add critical signal threshold level James Prestwood
2024-08-23 16:07   ` Denis Kenzior
2024-08-19 17:51 ` [PATCH v2 4/8] station: emit property changed for ConnectedAccessPoint James Prestwood
2024-08-23 16:10   ` Denis Kenzior [this message]
2024-08-19 17:51 ` [PATCH v2 5/8] station: add Affinities DBus property James Prestwood
2024-08-19 17:51 ` [PATCH v2 6/8] station: Use Affinities property to change roaming threshold James Prestwood
2024-08-19 17:51 ` [PATCH v2 7/8] auto-t: add affinities property for station, and extended_service_set James Prestwood
2024-08-19 17:51 ` [PATCH v2 8/8] auto-t: add tests for Affinities behavior James Prestwood
2024-08-23 16:03 ` [PATCH v2 1/8] doc: Document station Affinities property Denis Kenzior
2024-08-23 16:09   ` James Prestwood
2024-08-23 16:11     ` Denis Kenzior

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=e8ed4323-4ec3-43d5-be0c-768596430911@gmail.com \
    --to=denkenz@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