From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v4 1/3] util: add scan_freq_set_copy_bands
Date: Fri, 5 Aug 2022 11:54:55 -0500 [thread overview]
Message-ID: <66f0e017-d0df-c0a3-1871-d4e80c7e8bae@gmail.com> (raw)
In-Reply-To: <20220804220249.508207-1-prestwoj@gmail.com>
Hi James,
On 8/4/22 17:02, James Prestwood wrote:
> This creates a new scan_freq_set from an input set which only contains
> frequencies from bands included in the mask.
> ---
> src/util.c | 21 +++++++++++++++++++++
> src/util.h | 2 ++
> 2 files changed, 23 insertions(+)
<snip>
> +struct scan_freq_set *scan_freq_set_copy_bands(const struct scan_freq_set *set,
> + uint32_t band_mask);
I renamed this scan_freq_set_clone() and applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2022-08-05 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 22:02 [PATCH v4 1/3] util: add scan_freq_set_copy_bands James Prestwood
2022-08-04 22:02 ` [PATCH v4 2/3] scan: split full scans by band to enable 6GHz James Prestwood
2022-08-05 17:03 ` Denis Kenzior
2022-08-04 22:02 ` [PATCH v4 3/3] scan: watch for regdom updates " James Prestwood
2022-08-05 16:54 ` 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=66f0e017-d0df-c0a3-1871-d4e80c7e8bae@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