From: Steven Rostedt <rostedt@goodmis.org>
To: Shuvam Pandey <shuvampandey1@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
David Gow <david@davidgow.net>
Subject: Re: [PATCH v2] seq_buf: export seq_buf_putmem_hex() and add KUnit tests
Date: Wed, 8 Apr 2026 16:09:28 -0400 [thread overview]
Message-ID: <20260408160928.32ce8554@gandalf.local.home> (raw)
In-Reply-To: <20260408144449.57375-1-shuvampandey1@gmail.com>
On Wed, 8 Apr 2026 20:29:49 +0545
Shuvam Pandey <shuvampandey1@gmail.com> wrote:
> seq_buf: export seq_buf_putmem_hex() and add KUnit tests
>
> The seq_buf KUnit suite does not exercise seq_buf_putmem_hex().
>
> Add one test for the len > 8 chunking path and one overflow test
> where a later chunk no longer fits in the buffer.
>
> Export seq_buf_putmem_hex() as well so SEQ_BUF_KUNIT_TEST=m links
> cleanly. Without the export, modpost reports seq_buf_putmem_hex as
> undefined when seq_buf_kunit is built as a module.
>
Please always send a new version as its own thread and not as a reply to
the old version.
Also, for tracing and seq_buf, use capital letters in the subject:
seq_buf: Export seq_buf_putmem_hex() and add KUnit tests
> Signed-off-by: Shuvam Pandey <shuvampandey1@gmail.com>
> ---
> v2:
This should be:
Changes since v1: https://lore.kernel.org/all/20260406033728.25998-1-shuvampandey1@gmail.com/
> - export seq_buf_putmem_hex() so SEQ_BUF_KUNIT_TEST=m links cleanly
> - validate with a fresh arm64 build using CONFIG_KUNIT=y and CONFIG_SEQ_BUF_KUNIT_TEST=m
>
> lib/seq_buf.c | 1 +
> lib/tests/seq_buf_kunit.c | 34 ++++++++++++++++++++++++++++++++++
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: Shuvam Pandey <shuvampandey1@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v2] seq_buf: export seq_buf_putmem_hex() and add KUnit tests
Date: Wed, 8 Apr 2026 16:09:36 -0400 [thread overview]
Message-ID: <20260408160928.32ce8554@gandalf.local.home> (raw)
Message-ID: <20260408200936.G-vcbA7Rjvx1RRAj9Kg62Q_PjcWlxaEiHKNp01MpdII@z> (raw)
In-Reply-To: <20260408144449.57375-1-shuvampandey1@gmail.com>
On Wed, 8 Apr 2026 20:29:49 +0545
Shuvam Pandey <shuvampandey1@gmail.com> wrote:
> seq_buf: export seq_buf_putmem_hex() and add KUnit tests
>
> The seq_buf KUnit suite does not exercise seq_buf_putmem_hex().
>
> Add one test for the len > 8 chunking path and one overflow test
> where a later chunk no longer fits in the buffer.
>
> Export seq_buf_putmem_hex() as well so SEQ_BUF_KUNIT_TEST=m links
> cleanly. Without the export, modpost reports seq_buf_putmem_hex as
> undefined when seq_buf_kunit is built as a module.
>
Please always send a new version as its own thread and not as a reply to
the old version.
Also, for tracing and seq_buf, use capital letters in the subject:
seq_buf: Export seq_buf_putmem_hex() and add KUnit tests
> Signed-off-by: Shuvam Pandey <shuvampandey1@gmail.com>
> ---
> v2:
This should be:
Changes since v1: https://lore.kernel.org/all/20260406033728.25998-1-shuvampandey1@gmail.com/
> - export seq_buf_putmem_hex() so SEQ_BUF_KUNIT_TEST=m links cleanly
> - validate with a fresh arm64 build using CONFIG_KUNIT=y and CONFIG_SEQ_BUF_KUNIT_TEST=m
>
> lib/seq_buf.c | 1 +
> lib/tests/seq_buf_kunit.c | 34 ++++++++++++++++++++++++++++++++++
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2026-04-08 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 3:37 [PATCH] seq_buf: add KUnit tests for seq_buf_putmem_hex() Shuvam Pandey
2026-04-08 11:39 ` kernel test robot
2026-04-08 14:44 ` [PATCH v2] seq_buf: export seq_buf_putmem_hex() and add KUnit tests Shuvam Pandey
2026-04-08 20:09 ` Steven Rostedt [this message]
2026-04-08 20:09 ` Steven Rostedt
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=20260408160928.32ce8554@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=david@davidgow.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=shuvampandey1@gmail.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