From: Randy Dunlap <rdunlap@infradead.org>
To: Steven Rostedt <rostedt@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas.schier@linux.dev>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v6 2/3] tracing: Add a tracepoint verification check at build time
Date: Wed, 20 Aug 2025 13:12:22 -0700 [thread overview]
Message-ID: <88b25b9d-911a-4419-b1a6-e6ae38d499ba@infradead.org> (raw)
In-Reply-To: <20250820174828.080947631@kernel.org>
On 8/20/25 10:47 AM, Steven Rostedt wrote:
> +/**
> + * for_each_shdr_str - iterator that reads strings that are in an ELF section.
> + * @len: "int" to hold the length of the current string
> + * @ehdr: A pointer to the ehdr of the ELF file
> + * @sec: The section that has the strings to iterater on
iterate> + *
> + * This is a for loop that iterates over all the nul terminated strings
> + * that are in a given ELF section. The variable "str" will hold
> + * the current string for each iteration and the passed in @len will
> + * contain theh strlen() of that string.
the
> + */
--
~Randy
next prev parent reply other threads:[~2025-08-20 20:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 17:47 [PATCH v6 0/3] tracepoints: Add warnings for unused tracepoints and trace events Steven Rostedt
2025-08-20 17:47 ` [PATCH v6 1/3] sorttable: Move ELF parsing into scripts/elf-parse.[ch] Steven Rostedt
2025-08-20 17:47 ` [PATCH v6 2/3] tracing: Add a tracepoint verification check at build time Steven Rostedt
2025-08-20 20:12 ` Randy Dunlap [this message]
2025-08-20 20:19 ` Steven Rostedt
2025-08-20 20:27 ` Randy Dunlap
2025-08-23 17:54 ` kernel test robot
2025-08-20 17:47 ` [PATCH v6 3/3] tracepoint: Do not warn for unused event that is exported 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=88b25b9d-911a-4419-b1a6-e6ae38d499ba@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nicolas.schier@linux.dev \
--cc=rostedt@kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).