From: "Nemanov, Michael" <michael.nemanov@ti.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Khan, Sabeeh" <sabeeh-khan@ti.com>
Subject: Re: [RFC PATCH 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family
Date: Mon, 13 May 2024 14:27:37 +0300 [thread overview]
Message-ID: <8c301a6d-a5a5-4821-82a8-5ea241b5159d@ti.com> (raw)
In-Reply-To: <87cypqjjpw.fsf@kernel.org>
On 5/13/2024 9:42 AM, Kalle Valo wrote:
[...]
> I didn't review this yet but decided to do some build testing and it
> doesn't even build:
>
> drivers/net/wireless/ti/cc33xx/debugfs.c: In function 'cc33xx_debugfs_add_files_helper':
> drivers/net/wireless/ti/cc33xx/debugfs.h:37:37: error: 'cc' undeclared (first use in this function)
>
> I also see some warnings from GCC. I pushed the patches to a pending
> branch so most likely you get reports from kbuild bot:
[...]
Sorry, I did not test with CONFIG_CFG80211_CERTIFICATION_ONUS=y and
missed it. I will also make sure to build with W=1 and fix everything it
throws.
prev parent reply other threads:[~2024-05-13 11:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 18:32 [RFC PATCH 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 01/17] Add cc33xx.h, cc33xx_i.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 02/17] Add debug.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 03/17] Add sdio.c, io.c, io.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 04/17] Add cmd.c, cmd.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 05/17] Add acx.c, acx.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 06/17] Add event.c, event.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 07/17] Add boot.c, boot.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 08/17] Add main.c michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 09/17] Add rx.c, rx.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 10/17] Add tx.c, tx.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 11/17] Add init.c, init.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 12/17] Add debugfs.c, debugfs.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 13/17] Add scan.c, scan.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 14/17] Add conf.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 15/17] Add ps.c, ps.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 16/17] Add testmode.c, testmode.h michael.nemanov
2024-05-12 18:32 ` [RFC PATCH 17/17] Add Kconfig, Makefile and integrate into wireless/ti folder michael.nemanov
2024-05-13 6:42 ` [RFC PATCH 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family Kalle Valo
2024-05-13 11:27 ` Nemanov, Michael [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=8c301a6d-a5a5-4821-82a8-5ea241b5159d@ti.com \
--to=michael.nemanov@ti.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).