All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Schnelle <svens@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] few fixes for synthetic trace events
Date: Wed, 16 Aug 2023 11:08:52 +0200	[thread overview]
Message-ID: <yt9dcyzn9wwr.fsf@linux.ibm.com> (raw)
In-Reply-To: <20230810060538.1350348-1-svens@linux.ibm.com> (Sven Schnelle's message of "Thu, 10 Aug 2023 08:05:35 +0200")

Sven Schnelle <svens@linux.ibm.com> writes:

> Hi Steven,
>
> I'm now sending these patches in one patchset, because the second patch
> has a dependeny on the union vs. cast fix.
>
> Changes in v3:
> - remove superfluous struct around union trace_synth_field
>
> Changes in v2:
> - cosmetic changes
> - add struct trace_dynamic_info to include/linux/trace_events.h
>
> Sven Schnelle (3):
>   tracing/synthetic: use union instead of casts
>   tracing/synthetic: skip first entry for stack traces
>   tracing/synthetic: allocate one additional element for size
>
>  include/linux/trace_events.h      |  11 ++++
>  kernel/trace/trace.h              |   8 +++
>  kernel/trace/trace_events_synth.c | 103 ++++++++++++------------------
>  3 files changed, 60 insertions(+), 62 deletions(-)

Gentle ping? We're still seeing a lot of KASAN warnings.

  parent reply	other threads:[~2023-08-16  9:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10  6:05 [PATCH v3 0/3] few fixes for synthetic trace events Sven Schnelle
2023-08-10  6:05 ` [PATCH v3 1/3] tracing/synthetic: use union instead of casts Sven Schnelle
2023-09-08 19:44   ` Steven Rostedt
2023-08-10  6:05 ` [PATCH v3 2/3] tracing/synthetic: skip first entry for stack traces Sven Schnelle
2023-08-10  6:05 ` [PATCH v3 3/3] tracing/synthetic: allocate one additional element for size Sven Schnelle
2023-08-16  9:08 ` Sven Schnelle [this message]
2023-08-16 15:11   ` [PATCH v3 0/3] few fixes for synthetic trace events 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=yt9dcyzn9wwr.fsf@linux.ibm.com \
    --to=svens@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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 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.