From: sashiko-bot@kernel.org
To: "Rodrigo Alencar" <rodrigo.alencar@analog.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v9 07/17] iio: test: add kunit tests for channel prefix naming generation
Date: Wed, 22 Jul 2026 16:13:52 +0000 [thread overview]
Message-ID: <20260722161353.48A111F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260722-ad9910-iio-driver-v9-7-459d1df5ac56@analog.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `iio-test-channel-prefix` KUnit test module is missing a `MODULE_LICENSE()` declaration, which will cause it to taint the kernel and fail to load when compiled as a loadable module.
--
--- Patch [7]: [PATCH v9 07/17] iio: test: add kunit tests for channel prefix naming generation ---
commit cea50e2c0ecc39138633c2f38aadeebe93da4611
Author: Rodrigo Alencar <rodrigo.alencar@analog.com>
iio: test: add kunit tests for channel prefix naming generation
This commit adds a KUnit test suite for the __iio_chan_prefix_emit() helper
function. It tests various iio_shared_by modes, differential and modified
channel configurations, and exercises known error paths.
> diff --git a/drivers/iio/test/iio-test-channel-prefix.c b/drivers/iio/test/iio-test-channel-prefix.c
> new file mode 100644
> index 0000000000000..d049e4222c40e
> --- /dev/null
> +++ b/drivers/iio/test/iio-test-channel-prefix.c
[ ... ]
> +static struct kunit_suite iio_channel_prefix_test_suite = {
> + .name = "iio-channel-prefix",
> + .test_cases = iio_chan_prefix_test_cases,
> +};
> +
> +kunit_test_suite(iio_channel_prefix_test_suite);
> +
> +MODULE_IMPORT_NS("EXPORTED_FOR_KUNIT_TESTING");
[Severity: Medium]
Is a MODULE_LICENSE() declaration missing at the end of this file?
Because CONFIG_IIO_CHANNEL_PREFIX_KUNIT_TEST is defined as a tristate in
the Kconfig, this test can be compiled as a loadable module.
Without a MODULE_LICENSE() declaration, won't this taint the kernel and fail
to load due to unresolved GPL-exported symbols from the core KUnit framework
(such as __kunit_test_suites_init)?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260722-ad9910-iio-driver-v9-0-459d1df5ac56@analog.com?part=7
next prev parent reply other threads:[~2026-07-22 16:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 15:50 [PATCH v9 00/17] AD9910 Direct Digital Synthesizer Rodrigo Alencar via B4 Relay
2026-07-22 15:50 ` [PATCH v9 01/17] iio: ABI: add attributes for altcurrent channels Rodrigo Alencar via B4 Relay
2026-07-22 15:50 ` [PATCH v9 02/17] iio: ABI: raw, scale and offset for frequency/phase channels Rodrigo Alencar via B4 Relay
2026-07-22 15:50 ` [PATCH v9 03/17] iio: ABI: add parent entry for iio channels Rodrigo Alencar via B4 Relay
2026-07-22 15:50 ` [PATCH v9 04/17] iio: add IIO_FREQUENCY channel type Rodrigo Alencar via B4 Relay
2026-07-22 15:50 ` [PATCH v9 05/17] iio: core: support 64-bit register through debugfs Rodrigo Alencar via B4 Relay
2026-07-22 15:50 ` [PATCH v9 06/17] iio: core: create local __iio_chan_prefix_emit() for reuse Rodrigo Alencar via B4 Relay
2026-07-22 15:50 ` [PATCH v9 07/17] iio: test: add kunit tests for channel prefix naming generation Rodrigo Alencar via B4 Relay
2026-07-22 16:13 ` sashiko-bot [this message]
2026-07-22 15:50 ` [PATCH v9 08/17] iio: core: add hierarchical channel relationships Rodrigo Alencar via B4 Relay
2026-07-22 15:50 ` [PATCH v9 09/17] dt-bindings: iio: frequency: add ad9910 Rodrigo Alencar via B4 Relay
2026-07-22 15:50 ` [PATCH v9 10/17] iio: frequency: ad9910: initial driver implementation Rodrigo Alencar via B4 Relay
2026-07-22 16:24 ` sashiko-bot
2026-07-22 15:50 ` [PATCH v9 11/17] iio: frequency: ad9910: add basic parallel port support Rodrigo Alencar via B4 Relay
2026-07-22 15:50 ` [PATCH v9 12/17] iio: frequency: ad9910: add digital ramp generator support Rodrigo Alencar via B4 Relay
2026-07-22 15:50 ` [PATCH v9 13/17] iio: frequency: ad9910: add RAM mode support Rodrigo Alencar via B4 Relay
2026-07-22 16:44 ` sashiko-bot
2026-07-22 15:50 ` [PATCH v9 14/17] iio: frequency: ad9910: add output shift keying support Rodrigo Alencar via B4 Relay
2026-07-22 15:50 ` [PATCH v9 15/17] iio: frequency: ad9910: show channel priority in debugfs Rodrigo Alencar via B4 Relay
2026-07-22 16:52 ` sashiko-bot
2026-07-22 15:50 ` [PATCH v9 16/17] iio: ABI: add docs for ad9910 sysfs and debugfs entries Rodrigo Alencar via B4 Relay
2026-07-22 16:50 ` sashiko-bot
2026-07-22 15:50 ` [PATCH v9 17/17] docs: iio: add documentation for ad9910 driver Rodrigo Alencar via B4 Relay
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=20260722161353.48A111F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rodrigo.alencar@analog.com \
--cc=sashiko-reviews@lists.linux.dev \
/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