Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz at gmail.com>
To: iwd at lists.01.org
Subject: Re: [PATCH] knownnetworks: update known frequencies maximum to 7115
Date: Thu, 03 Mar 2022 12:57:34 -0600	[thread overview]
Message-ID: <20dc4e75-fa02-1d4b-fd92-68e92cd47f36@gmail.com> (raw)
In-Reply-To: 20220303172234.3447411-1-prestwoj@gmail.com

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

Hi James,

On 3/3/22 11:22, James Prestwood wrote:
> With the addition of 6GHz '6000' is no longer the maximum frequency
> that could be in .known_network.freq.
> ---
>   src/knownnetworks.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/src/knownnetworks.c b/src/knownnetworks.c
> index 87df8b4d..fc024333 100644
> --- a/src/knownnetworks.c
> +++ b/src/knownnetworks.c
> @@ -856,7 +856,7 @@ static struct l_queue *known_frequencies_from_string(char *freq_set_str)
>   
>   		t = strtoul(freq_set_str, &freq_set_str, 10);
>   
> -		if (unlikely(errno == ERANGE || !t || t > 6000))
> +		if (unlikely(errno == ERANGE || !t || t > 7115))

Do you want to use band_freq_to_channel here instead?  That one checks the valid 
freqs...

>   			goto error;
>   
>   		known_freq = l_new(struct known_frequency, 1);
> 

Regards,
-Denis

             reply	other threads:[~2022-03-03 18:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 18:57 Denis Kenzior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-03 20:23 [PATCH] knownnetworks: update known frequencies maximum to 7115 James Prestwood
2022-03-03 17:59 Diederik de Haas
2022-03-03 17:22 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=20dc4e75-fa02-1d4b-fd92-68e92cd47f36@gmail.com \
    --to=iwd@lists.linux.dev \
    /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