From: Kalle Valo <kvalo@kernel.org>
To: <michael.nemanov@ti.com>
Cc: <linux-wireless@vger.kernel.org>, <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 09:42:51 +0300 [thread overview]
Message-ID: <87cypqjjpw.fsf@kernel.org> (raw)
In-Reply-To: <20240512183247.2190242-1-michael.nemanov@ti.com> (michael nemanov's message of "Sun, 12 May 2024 21:32:30 +0300")
<michael.nemanov@ti.com> writes:
> From: Michael Nemanov <michael.nemanov@ti.com>
>
> This series adds support for CC33xx which is a new family of WLAN IEEE802.11 a/b/g/n/ax
> and BLE 5.4 transceivers by Texas Instruments. These devices are 20MHz single spatial stream
> enabling STA (IEEE802.11ax) and AP (IEEE802.11n only) roles as well as both roles simultaneously.
> Communication to the CC33xx is done via 4-bit SDIO with two extra
> GPIOs: Enable and Interrupt.
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:
https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/log/?h=pending
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-05-13 6:42 UTC|newest]
Thread overview: 23+ 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:51 ` kernel test robot
2024-05-13 7:46 ` kernel test robot
2024-05-14 4:33 ` kernel test robot
2024-05-13 6:42 ` Kalle Valo [this message]
2024-05-13 11:27 ` [RFC PATCH 00/17] wifi: cc33xx: Add driver for new TI CC33xx wireless device family Nemanov, Michael
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=87cypqjjpw.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michael.nemanov@ti.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.