From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jeff Chen <jeff.chen_1@nxp.com>, linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, briannorris@chromium.org,
johannes@sipsolutions.net, francesco@dolcini.it,
tsung-hsien.hsieh@nxp.com, s.hauer@pengutronix.de
Subject: Re: [PATCH v8 20/22] wifi: nxpwifi: add NXP vendor and IW61x device IDs to sdio_ids.h
Date: Fri, 5 Dec 2025 08:46:31 +0100 [thread overview]
Message-ID: <98cc00f5-344e-4eaa-849f-091d1699dcbc@kernel.org> (raw)
In-Reply-To: <20251205065545.3325032-21-jeff.chen_1@nxp.com>
On 05/12/2025 07:55, Jeff Chen wrote:
> Register NXP's SDIO vendor ID (0x0471) and IW61x device ID (0x0205)
> in the global SDIO ID list. This allows the nxpwifi SDIO driver to
> match and bind to supported NXP Wi-Fi chips via the SDIO bus.
Only limited review because you did not care to even cc maintainers -
don't describe drivers. Describe hardware.
>
> Signed-off-by: Jeff Chen <jeff.chen_1@nxp.com>
> ---
> .../bindings/net/wireless/nxp,iw61x.yaml | 85 +++++++++++++++++++
> include/linux/mmc/sdio_ids.h | 3 +
> 2 files changed, 88 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/wireless/nxp,iw61x.yaml
>
> diff --git a/Documentation/devicetree/bindings/net/wireless/nxp,iw61x.yaml b/Documentation/devicetree/bindings/net/wireless/nxp,iw61x.yaml
> new file mode 100644
> index 000000000000..358714796868
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/wireless/nxp,iw61x.yaml
> @@ -0,0 +1,85 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/wireless/nxp,iw61x.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NXP IW61x SDIO devices
> +
> +maintainers:
> + - Jeff Chen <jeff.chen_1@nxp.com>
> +
> +description:
> + This node provides properties for describing the NXP SDIO wireless device.
Describe hardware, not DT. We know how DT works.
Not reviewing the rest, NAK.
Please run scripts/checkpatch.pl on the patches and fix reported
warnings. After that, run also 'scripts/checkpatch.pl --strict' on the
patches and (probably) fix more warnings. Some warnings can be ignored,
especially from --strict run, but the code here looks like it needs a
fix. Feel free to get in touch if the warning is not clear.
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.
Please kindly resend and include all necessary To/Cc entries.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-05 7:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 6:55 [PATCH v8 00/22] wifi: nxpwifi: create nxpwifi to support Jeff Chen
2025-12-05 6:55 ` [PATCH v8 01/22] wifi: nxpwifi: Add 802.11n support for client and AP modes Jeff Chen
2025-12-05 6:55 ` [PATCH v8 02/22] wifi: nxpwifi: add initial support for 802.11ac Jeff Chen
2025-12-05 6:55 ` [PATCH v8 03/22] wifi: nxpwifi: add initial support for 802.11ax Jeff Chen
2025-12-05 6:55 ` [PATCH v8 04/22] wifi: nxpwifi: add support for 802.11h (DFS and TPC) Jeff Chen
2025-12-05 6:55 ` [PATCH v8 05/22] wifi: nxpwifi: add support for WMM Jeff Chen
2025-12-05 6:55 ` [PATCH v8 06/22] wifi: nxpwifi: add scan support Jeff Chen
2025-12-05 6:55 ` [PATCH v8 07/22] wifi: nxpwifi: add join and association support Jeff Chen
2025-12-05 6:55 ` [PATCH v8 08/22] wifi: nxpwifi: add channel/frequency/power (cfp) support Jeff Chen
2025-12-05 6:55 ` [PATCH v8 09/22] wifi: nxpwifi: add configuration support Jeff Chen
2025-12-05 6:55 ` [PATCH v8 10/22] wifi: nxpwifi: implement cfg80211 ops for STA and AP modes Jeff Chen
2025-12-05 6:55 ` [PATCH v8 11/22] wifi: nxpwifi: add firmware command and TLV definitions Jeff Chen
2025-12-05 6:55 ` [PATCH v8 12/22] wifi: nxpwifi: introduce command and event handling infrastructure Jeff Chen
2025-12-05 7:11 ` Sascha Hauer
2025-12-05 8:40 ` Jeff Chen
2025-12-05 6:55 ` [PATCH v8 13/22] wifi: nxpwifi: add data path support for STA and AP modes Jeff Chen
2025-12-05 6:55 ` [PATCH v8 14/22] wifi: nxpwifi: add debugfs support for diagnostics and testing Jeff Chen
2025-12-05 6:55 ` [PATCH v8 15/22] wifi: nxpwifi: add ethtool support for Wake-on-LAN Jeff Chen
2025-12-05 6:55 ` [PATCH v8 16/22] wifi: nxpwifi: add utility and IE handling support Jeff Chen
2025-12-05 6:55 ` [PATCH v8 17/22] wifi: nxpwifi: add driver initialization and shutdown support Jeff Chen
2025-12-05 6:55 ` [PATCH v8 18/22] wifi: nxpwifi: add core driver implementation Jeff Chen
2025-12-05 6:55 ` [PATCH v8 19/22] wifi: nxpwifi: add initial SDIO bus driver support Jeff Chen
2025-12-05 7:51 ` Krzysztof Kozlowski
2025-12-05 6:55 ` [PATCH v8 20/22] wifi: nxpwifi: add NXP vendor and IW61x device IDs to sdio_ids.h Jeff Chen
2025-12-05 7:46 ` Krzysztof Kozlowski [this message]
2025-12-05 6:55 ` [PATCH v8 21/22] wifi: nxpwifi: add Kconfig and Makefile for kernel integration Jeff Chen
2025-12-05 6:55 ` [PATCH v8 22/22] wifi: nxpwifi: add MAINTAINERS entry for nxpwifi driver Jeff Chen
2025-12-16 14:52 ` [v8,00/22] wifi: nxpwifi: create nxpwifi to support Romit Chatterjee
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=98cc00f5-344e-4eaa-849f-091d1699dcbc@kernel.org \
--to=krzk@kernel.org \
--cc=briannorris@chromium.org \
--cc=francesco@dolcini.it \
--cc=jeff.chen_1@nxp.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=tsung-hsien.hsieh@nxp.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