From: Steven Rostedt <rostedt@goodmis.org>
To: linux-trace-devel@vger.kernel.org
Subject: [PATCH 0/2] libtracefs: Minor formating updates to options code
Date: Tue, 02 Feb 2021 14:54:58 -0500 [thread overview]
Message-ID: <20210202195458.176697224@goodmis.org> (raw)
This is based on top of the options patches:
https://patchwork.kernel.org/project/linux-trace-devel/list/?series=418299
This adds a BUILD_BUG_ON() and ARRAY_SIZE helper macros and
structures the options_map slightly different.
No functional changes.
Steven Rostedt (VMware) (2):
tracefs: Use new BUILD_BUG_ON() and ARRAY_SIZE() macros for options_map intergity
libtracefs: Have the options_map elements be each on their own line
----
include/tracefs-local.h | 6 ++++++
src/tracefs-tools.c | 56 ++++++++++++++++++++++++++++++++++++++++---------
2 files changed, 52 insertions(+), 10 deletions(-)
next reply other threads:[~2021-02-02 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 19:54 Steven Rostedt [this message]
2021-02-02 19:54 ` [PATCH 1/2] tracefs: Use new BUILD_BUG_ON() and ARRAY_SIZE() macros for options_map intergity Steven Rostedt
2021-02-02 19:55 ` [PATCH 2/2] libtracefs: Have the options_map elements be each on their own line 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=20210202195458.176697224@goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.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).