From: Ross Zwisler <zwisler@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
Stevie Alvarez <stevie.6strings@gmail.com>
Subject: Re: [PATCH] libtraceeval: Add traceeval_init_data_size()
Date: Mon, 2 Oct 2023 14:25:43 -0600 [thread overview]
Message-ID: <20231002202543.GJ1532181@google.com> (raw)
In-Reply-To: <20230927090904.396273fa@rorschach.local.home>
On Wed, Sep 27, 2023 at 09:09:04AM -0400, Steven Rostedt wrote:
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
>
> In the future, the traceeval_type and traceeval_data may need to include
> more information and be expanded. If that happens, it will break backward
> compatibility for older applications using the newer library.
>
> To be able to handle backward compatibility in this situation, have the
> traceeval_init() turn into traceeval_init_data_size() which takes the
> sizeof struct traceeval_type and struct traceeval_data. Make
> traceeval_init() into a macro that calls this function passing in the
> sizeof(struct traceeval_type) and sizeof(struct traceeval_data). This way
> if the sizes change for either one, the new code will know if the
> application is using the new interface or the older one, and can
> can keep the older one still functioning properly.
>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Reviewed-by: Ross Zwisler <zwisler@google.com>
prev parent reply other threads:[~2023-10-02 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 13:09 [PATCH] libtraceeval: Add traceeval_init_data_size() Steven Rostedt
2023-10-02 20:25 ` Ross Zwisler [this message]
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=20231002202543.GJ1532181@google.com \
--to=zwisler@google.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stevie.6strings@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 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.