From: Steven Rostedt <rostedt@goodmis.org>
To: John Koepi <john.koepi@gmail.com>
Cc: linux-trace-devel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH bpf] traceevent: ignore __attribute__ in fields format
Date: Wed, 15 Jan 2020 14:31:08 -0500 [thread overview]
Message-ID: <20200115143108.026cc2c1@gandalf.local.home> (raw)
In-Reply-To: <CAJ8z9b0fHwOUgF_AgXED3wuZpOVbQTfGA3WkNbNFCmiY_Br3Tw@mail.gmail.com>
On Wed, 15 Jan 2020 20:47:47 +0200
John Koepi <john.koepi@gmail.com> wrote:
> I am not sure this is the right mailing list (I was not sure about
> @netdev). If it is not - I am sorry, I can resend it. The test for
> this change is at https://github.com/sitano/traceevent_attribute.
>
It's fine to send it here. It's in my queue to look at.
Thanks!
-- Steve
prev parent reply other threads:[~2020-01-15 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 17:07 traceevent support for kernels with CONFIG_GCC_PLUGIN_STRUCTLEAK=y John Koepi
2019-12-12 17:25 ` Steven Rostedt
2019-12-14 15:38 ` John Koepi
2020-01-15 18:06 ` [PATCH bpf] traceevent: ignore __attribute__ in fields format Ivan Prisyazhnyy
2020-01-15 18:47 ` John Koepi
2020-01-15 19:31 ` Steven Rostedt [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=20200115143108.026cc2c1@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.koepi@gmail.com \
--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).