From: Steven Rostedt <rostedt@goodmis.org>
To: Wan Jiabing <wanjiabing@vivo.com>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, kael_w@yeah.net
Subject: Re: [PATCH] linux/trace_events.h: Remove duplicate struct declaration
Date: Mon, 29 Mar 2021 23:29:01 -0400 [thread overview]
Message-ID: <20210329232901.038ecb4f@gandalf.local.home> (raw)
In-Reply-To: <20210330015517.2264721-1-wanjiabing@vivo.com>
On Tue, 30 Mar 2021 09:55:17 +0800
Wan Jiabing <wanjiabing@vivo.com> wrote:
> struct trace_array is declared twice. One has been declared
> at forward struct declaration. Remove the duplicate.
> And sort these forward declarations alphabetically.
Um, no that's not how we sort things.
>
> Signed-off-by: Wan Jiabing <wanjiabing@vivo.com>
> ---
> include/linux/trace_events.h | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/trace_events.h b/include/linux/trace_events.h
> index 28e7af1406f2..29ae3ec5cab9 100644
> --- a/include/linux/trace_events.h
> +++ b/include/linux/trace_events.h
> @@ -10,11 +10,11 @@
> #include <linux/perf_event.h>
> #include <linux/tracepoint.h>
>
> -struct trace_array;
> struct array_buffer;
> -struct tracer;
> -struct dentry;
> struct bpf_prog;
> +struct dentry;
> +struct tracer;
> +struct trace_array;
NAK to the above. If anything, we sort it by length. But the above doesn't
need to be touched.
>
> const char *trace_print_flags_seq(struct trace_seq *p, const char *delim,
> unsigned long flags,
> @@ -404,7 +404,6 @@ trace_get_fields(struct trace_event_call *event_call)
> return event_call->class->get_fields(event_call);
> }
>
> -struct trace_array;
This part is fine.
Thanks,
-- Steve
> struct trace_subsystem_dir;
>
> enum {
next prev parent reply other threads:[~2021-03-30 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 1:55 Wan Jiabing
2021-03-30 3:29 ` Steven Rostedt [this message]
2021-03-30 3:43 ` 万家兵
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=20210329232901.038ecb4f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=kael_w@yeah.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=wanjiabing@vivo.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
all inboxes | Powered by JetHome®