From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] [brcmfmac] Add support for 6G bands
Date: Fri, 20 Oct 2023 20:37:34 +0200 [thread overview]
Message-ID: <5f634ac5-3745-aa5c-612a-0f4efc8764fd@broadcom.com> (raw)
In-Reply-To: <CAF4BwTUTmUd0c-y_NfSi9WkCnDO9bhtpx03Aai1ByH5auq9YXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
On 10/20/2023 6:35 PM, Daniel Berlin wrote:
>>> @@ -6965,6 +7066,10 @@ static int brcmf_construct_chaninfo(struct brcmf_cfg80211_info *cfg,
>>> for (i = 0; i < band->n_channels; i++)
>>> band->channels[i].flags = IEEE80211_CHAN_DISABLED;
>>> band = wiphy->bands[NL80211_BAND_5GHZ];
>>> + if (band)
>> Eh. Why is this conditional? We are creating all bands in the wiphy
>> instance so why the null check here?
>
> I just matched what was there, I can remove all of them if we want.
>
> (I'll take care of the rest of the comments between here)
I stumbled upon the bandlist usage later in this patch (I think) so we
do add bands only when the device supports them. Hence you can ignore my
comment here.
Regards,
Arend
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next prev parent reply other threads:[~2023-10-20 18:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1697650207.git.dberlin@dberlin.org>
[not found] ` <0b95944fcf047b3ec83cecb0c65ca24de43810fd.1697650207.git.dberlin@dberlin.org>
2023-10-20 9:57 ` [PATCH 1/5] [brcmfmac] Add support for encoding/decoding 6g chanspecs Arend van Spriel
2023-10-20 16:36 ` Daniel Berlin
2023-10-20 21:46 ` Jeff Johnson
2023-10-21 18:27 ` Arend van Spriel
[not found] ` <52c993fd93e13ac015be935a5284294c9a74ea8e.1697650207.git.dberlin@dberlin.org>
2023-10-20 9:58 ` [PATCH 2/5] [brcmfmac] Add support for 6G bands Arend van Spriel
2023-10-20 16:35 ` Daniel Berlin
2023-10-20 18:37 ` Arend van Spriel [this message]
2023-10-23 11:41 ` Daniel Berlin
2023-10-23 18:06 ` Arend Van Spriel
2023-10-23 18:09 ` Arend Van Spriel
[not found] ` <9bb36bcc0dbbbe6f991be30ec404b6e5197238ac.1697650207.git.dberlin@dberlin.org>
2023-10-20 9:58 ` [PATCH 3/5] wifi: brcmfmac: Add support for SCAN_V3 Arend van Spriel
[not found] ` <079882bf4a7c026547ecf8ad50a2b7a49ade7130.1697650207.git.dberlin@dberlin.org>
2023-10-20 9:59 ` [PATCH 4/5] wifi: brcmfmac: Support bss_info up to v112 Arend van Spriel
2023-10-20 17:31 ` Daniel Berlin
2023-10-31 14:04 ` Daniel Berlin
2023-10-31 16:27 ` Arend Van Spriel
2023-11-07 11:11 ` Hector Martin
2023-11-07 11:51 ` Arend van Spriel
2023-11-07 12:00 ` Daniel Berlin
2023-11-07 19:28 ` Arend van Spriel
[not found] ` <791863a231dca48234a3468b299d0bc71a85b6b0.1697650207.git.dberlin@dberlin.org>
2023-10-20 9:59 ` [PATCH 5/5] [brcmfmac] Add remaining support for 6G by supporting new scan structures Arend van Spriel
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=5f634ac5-3745-aa5c-612a-0f4efc8764fd@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=dberlin@dberlin.org \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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
all inboxes | Powered by JetHome®