From: Steven Rostedt <rostedt@goodmis.org>
To: Valentin Schneider <vschneid@redhat.com>
Cc: linux-trace-devel@vger.kernel.org,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Clark Williams <williams@redhat.com>,
Douglas RAILLARD <douglas.raillard@arm.com>
Subject: Re: [PATCH 1/2] libtraceevent: Add boiler-plate code for cpumask types
Date: Wed, 9 Nov 2022 19:06:34 -0500 [thread overview]
Message-ID: <20221109190634.1fd9200d@rorschach.local.home> (raw)
In-Reply-To: <20221018151630.1513535-2-vschneid@redhat.com>
On Tue, 18 Oct 2022 16:16:29 +0100
Valentin Schneider <vschneid@redhat.com> wrote:
> @@ -3484,6 +3498,11 @@ process_function(struct tep_event *event, struct tep_print_arg *arg,
> free_token(token);
> return process_bitmask(event, arg, tok);
> }
> + if (strcmp(token, "__get_cpumask") == 0 ||
> + strcmp(token, "__get_cpumask") == 0) {
Hmm, not sure what the difference between the above two are.
-- Steve
> + free_token(token);
> + return process_cpumask(event, arg, tok);
> + }
> if (strcmp(token, "__get_dynamic_array") == 0 ||
> strcmp(token, "__get_rel_dynamic_array") == 0 ||
> strcmp(token, "__get_sockaddr") == 0 ||
next prev parent reply other threads:[~2022-11-10 0:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 15:16 [PATCH 0/2] libtraceevent: Handling cpumask event fields Valentin Schneider
2022-10-18 15:16 ` [PATCH 1/2] libtraceevent: Add boiler-plate code for cpumask types Valentin Schneider
2022-11-10 0:06 ` Steven Rostedt [this message]
2022-11-11 16:32 ` Valentin Schneider
2022-11-15 21:10 ` Steven Rostedt
2022-11-16 11:29 ` Valentin Schneider
2022-10-18 15:16 ` [PATCH 2/2] libtraceevent: Pretty-print cpumask fields as a cpulist Valentin Schneider
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=20221109190634.1fd9200d@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=bristot@redhat.com \
--cc=douglas.raillard@arm.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=vschneid@redhat.com \
--cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).