From: "Nemanov, Michael" <michael.nemanov@ti.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Kalle Valo <kvalo@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-wireless@vger.kernel.org>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Sabeeh Khan <sabeeh-khan@ti.com>
Subject: Re: [PATCH v5 09/17] wifi: cc33xx: Add main.c
Date: Tue, 12 Nov 2024 17:34:43 +0200 [thread overview]
Message-ID: <2dbf1cba-0b16-413b-947e-dacf32c85687@ti.com> (raw)
In-Reply-To: <685d782d68bfc664c4fcc594dff96546ffc30e5f.camel@sipsolutions.net>
On 11/8/2024 1:42 PM, Johannes Berg wrote:
> Hi,
>
> reading through this anyway looking for mac80211 integration, so I'll
> nitpick too ... ;-)
>
...
>> + if (wlvif->sta.role_chan_type != NL80211_CHAN_HT40MINUS &&
>> + wlvif->sta.role_chan_type != NL80211_CHAN_HT40PLUS)
>> + ieee80211_connection_loss(cc33xx_wlvif_to_vif(wlvif));
>
> You seem to support HE (PPE thresholds above and all that), but then you
> still use CHAN_HT40MINUS/PLUS?! That seems ... rather wrong? You should
> probably track in terms of NL80211_CHAN_WIDTH_*, I'm not even sure how
> you get NL80211_CHAN_* values in the first place, mac80211 should never
> use them now?
>
Right, a leftover from wlcore. Since CC33xx is 20 MHz only device I'll
remove it.
...
>> +static inline void cc33xx_tx_watchdog_work(struct work_struct *work)
>> +{
>> + container_of(to_delayed_work(work), struct cc33xx, tx_watchdog_work);
>> +}
>
> I don't think that does what you think it does. Well, I don't know what
> you think it does, but ...
>
> Also there should be (almost) no inline in C files, and even if it were
> correct you'd probably just use it exactly once?
>
Agree, will get rid of inline in all functions.
...
>> +static int parse_control_message(struct cc33xx *cc,
>> + const u8 *buffer, size_t buffer_length)
>> +{
>> + u8 *const end_of_payload = (u8 *const)buffer + buffer_length;
>> + u8 *const start_of_payload = (u8 *const)buffer;
>
> I don't think the "u8 *const" is useful here, and the cast is awkward.
> If anything you'd want "const u8 *const" (which should make it not need
> the cast), but the const you have adds no value... do you even know what
> it means? ;-)
>
My intent was to express that start and end pointers are fixed and will
not change in the loop below. When reading this again I agree this hurts
more than it helps, I'll drop it.
const u8 *buffer in the prototype illustrates that parse_control_message
will not change the data so I'll keep it if there a re no objections.
>> + struct NAB_header *nab_header;
>
> surely checkpatch complained about CamelCase or so with the struct name
> like that?
>
Double-checked, no warnings from checkpatch:
----------------------------------------------
$ scripts/checkpatch.pl --codespell --strict
../../export/upstream/patch/v5-0009-wifi-cc33xx-Add-main.c.patch
WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
#44:
new file mode 100644
WARNING: Prefer "GPL" over "GPL v2" - see commit bf7fbeeae6db ("module:
Cure the MODULE_LICENSE "GPL" vs. "GPL v2" bogosity")
#5729: FILE: drivers/net/wireless/ti/cc33xx/main.c:5681:
+MODULE_LICENSE("GPL v2");
total: 0 errors, 2 warnings, 0 checks, 5687 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or
--fix-inplace.
../../export/upstream/patch/v5-0009-wifi-cc33xx-Add-main.c.patch has
style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
$
----------------------------------------------
Obviously will fix the definition.
Still going over all other items you referred to, will take a minute :)
Thanks and regards,
Michael.
next prev parent reply other threads:[~2024-11-12 15:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 12:51 [PATCH v5 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family Michael Nemanov
2024-11-07 12:51 ` [PATCH v5 01/17] dt-bindings: net: wireless: cc33xx: Add ti,cc33xx.yaml Michael Nemanov
2024-11-08 12:02 ` Krzysztof Kozlowski
2024-11-12 6:45 ` Nemanov, Michael
2024-11-19 9:15 ` Krzysztof Kozlowski
2024-11-19 12:10 ` Nemanov, Michael
2024-11-08 12:07 ` Krzysztof Kozlowski
2024-11-07 12:51 ` [PATCH v5 02/17] wifi: cc33xx: Add cc33xx.h, cc33xx_i.h Michael Nemanov
2024-11-07 12:51 ` [PATCH v5 03/17] wifi: cc33xx: Add debug.h Michael Nemanov
2024-11-07 12:51 ` [PATCH v5 04/17] wifi: cc33xx: Add sdio.c, io.c, io.h Michael Nemanov
2024-11-07 12:51 ` [PATCH v5 05/17] wifi: cc33xx: Add cmd.c, cmd.h Michael Nemanov
2024-11-08 16:25 ` Markus Elfring
2024-11-07 12:51 ` [PATCH v5 06/17] wifi: cc33xx: Add acx.c, acx.h Michael Nemanov
2024-11-07 12:51 ` [PATCH v5 07/17] wifi: cc33xx: Add event.c, event.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 08/17] wifi: cc33xx: Add boot.c, boot.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 09/17] wifi: cc33xx: Add main.c Michael Nemanov
2024-11-08 11:42 ` Johannes Berg
2024-11-11 11:38 ` Kalle Valo
2024-11-12 15:34 ` Nemanov, Michael [this message]
2024-11-12 15:39 ` Johannes Berg
2024-11-14 17:44 ` Nemanov, Michael
2024-12-01 9:47 ` Nemanov, Michael
2024-12-01 17:09 ` Nemanov, Michael
2024-11-07 12:52 ` [PATCH v5 10/17] wifi: cc33xx: Add rx.c, rx.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 11/17] wifi: cc33xx: Add tx.c, tx.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 12/17] wifi: cc33xx: Add init.c, init.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 13/17] wifi: cc33xx: Add scan.c, scan.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 14/17] wifi: cc33xx: Add conf.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 15/17] wifi: cc33xx: Add ps.c, ps.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 16/17] wifi: cc33xx: Add testmode.c, testmode.h Michael Nemanov
2024-11-07 12:52 ` [PATCH v5 17/17] wifi: cc33xx: Add Kconfig, Makefile Michael Nemanov
2025-04-29 16:38 ` [PATCH v5 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family Ezra Buehler
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=2dbf1cba-0b16-413b-947e-dacf32c85687@ti.com \
--to=michael.nemanov@ti.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=sabeeh-khan@ti.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
all inboxes | Powered by JetHome®