Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v3 1/7] wiphy: track GET_REG ID
Date: Thu, 4 Aug 2022 14:18:27 -0500	[thread overview]
Message-ID: <bdcaea9d-eb72-c759-9589-5c1e761485ea@gmail.com> (raw)
In-Reply-To: <20220804185112.457670-1-prestwoj@gmail.com>

Hi James,

On 8/4/22 13:51, James Prestwood wrote:
> Keep track of the GET_REG call so it can be canceled if the wiphy
> goes down.
> ---
>   src/wiphy.c | 11 +++++++++--
>   1 file changed, 9 insertions(+), 2 deletions(-)
> 
> v3:
>   * Moved this out into its own patch
> 

Patch 1,2,3 and 7 applied, thanks.

Regards,
-Denis


      parent reply	other threads:[~2022-08-04 19:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 18:51 [PATCH v3 1/7] wiphy: track GET_REG ID James Prestwood
2022-08-04 18:51 ` [PATCH v3 2/7] wiphy: dump wiphy's on regulatory domain change James Prestwood
2022-08-04 18:51 ` [PATCH v3 3/7] wiphy: add wiphy_regdom_is_updating James Prestwood
2022-08-04 18:51 ` [PATCH v3 4/7] station: do full passive scan if 6GHz is supported but disabled James Prestwood
2022-08-04 19:20   ` Denis Kenzior
2022-08-04 18:51 ` [PATCH v3 5/7] scan: split full scans by band to enable 6GHz James Prestwood
2022-08-04 18:51 ` [PATCH v3 6/7] scan: watch for regdom updates " James Prestwood
2022-08-04 18:51 ` [PATCH v3 7/7] wiphy: don't re-dump wiphy if the regdom didn't change James Prestwood
2022-08-04 19:18 ` Denis Kenzior [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=bdcaea9d-eb72-c759-9589-5c1e761485ea@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