From: sashiko-bot@kernel.org
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 5/7] tracing: Add a test for ftrace_parse_event_string()
Date: Thu, 13 Aug 2026 14:14:49 +0000 [thread overview]
Message-ID: <20260813141450.2D8251F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260813-tracing-cli-event-filter-v1-5-57c4e8029c86@linutronix.de>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The newly added module `trace_events_test.c` lacks a `MODULE_DESCRIPTION()` declaration. Since `CONFIG_EVENT_TRACING_TEST` is a tristate config, the code can be compiled as a module. Recent Linux kernels strictly enforce module descriptions, and omitting it results in a modpost warning (`WARNING: modpost: missing MODULE_DESCRIPTION() in kernel/trace/trace_events_test.o`). In automated CI environments that enforce zero warnings or build with `-Werror`, this will cause build failures.
--
--- Patch [5]: [PATCH RFC 5/7] tracing: Add a test for ftrace_parse_event_string() ---
commit 509c596a834391e59b26327382138635d44f58c9
Author: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
tracing: Add a test for ftrace_parse_event_string()
This commit adds a KUnit test for the ftrace_parse_event_string() function
to prevent regressions as the parsing logic is updated.
> diff --git a/kernel/trace/trace_events_test.c b/kernel/trace/trace_events_test.c
> new file mode 100644
> --- /dev/null
> +++ b/kernel/trace/trace_events_test.c
[ ... ]
> +static struct kunit_suite trace_events_test_suite = {
> + .name = "trace-events",
> + .test_cases = trace_events_test_cases,
> +};
> +kunit_test_suite(trace_events_test_suite);
> +
> +
> +MODULE_LICENSE("GPL");
> +MODULE_IMPORT_NS("EXPORTED_FOR_KUNIT_TESTING");
[Severity: Low]
Since CONFIG_EVENT_TRACING_TEST is a tristate config and this can be compiled
as a module, should a MODULE_DESCRIPTION() be added here?
Recent kernels emit a modpost warning (WARNING: modpost: missing
MODULE_DESCRIPTION() in kernel/trace/trace_events_test.o) when this is
omitted, which could cause build failures in automated CI environments that
enforce zero warnings.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260813-tracing-cli-event-filter-v1-0-57c4e8029c86@linutronix.de?part=5
next prev parent reply other threads:[~2026-08-13 14:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 14:07 [PATCH RFC 0/7] tracing: Parse filter from event string Thomas Weißschuh
2026-08-13 14:07 ` [PATCH RFC 1/7] tracing: Restore :mod: trailer after parsing in ftrace_set_clr_event() Thomas Weißschuh
2026-08-13 14:07 ` [PATCH RFC 2/7] tracing: Remove duplicate declaration of ftrace_set_clr_event() Thomas Weißschuh
2026-08-13 14:07 ` [PATCH RFC 3/7] tracing: Stop modifying the input buffer in ftrace_set_clr_event() Thomas Weißschuh
2026-08-13 14:15 ` sashiko-bot
2026-08-13 14:38 ` Steven Rostedt
2026-08-13 14:40 ` Thomas Weißschuh
2026-08-13 14:45 ` Steven Rostedt
2026-08-13 14:07 ` [PATCH RFC 4/7] tracing: Split the event string parsing logic into a dedicated function Thomas Weißschuh
2026-08-13 14:07 ` [PATCH RFC 5/7] tracing: Add a test for ftrace_parse_event_string() Thomas Weißschuh
2026-08-13 14:14 ` sashiko-bot [this message]
2026-08-13 14:07 ` [PATCH RFC 6/7] tracing: Add a filter argument to __ftrace_set_clr_event() Thomas Weißschuh
2026-08-13 14:07 ` [PATCH RFC 7/7] tracing: Parse filter from event string Thomas Weißschuh
2026-08-13 14:22 ` sashiko-bot
2026-08-13 16:22 ` Masami Hiramatsu
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=20260813141450.2D8251F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=thomas.weissschuh@linutronix.de \
/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.