From: Greg KH <gregkh@linuxfoundation.org>
To: George Guo <dongtai.guo@linux.dev>
Cc: tom.zanussi@linux.intel.com, stable@vger.kernel.org,
Namhyung Kim <namhyung@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
George Guo <guodongtai@kylinos.cn>
Subject: Re: [PATCH 4.19.y v5 1/2] tracing: Remove hist trigger synth_var_refs
Date: Fri, 19 Apr 2024 13:18:06 +0200 [thread overview]
Message-ID: <2024041946-primarily-panning-8fd1@gregkh> (raw)
In-Reply-To: <20240416015432.2282705-2-dongtai.guo@linux.dev>
On Tue, Apr 16, 2024 at 09:54:31AM +0800, George Guo wrote:
> From: Tom Zanussi <tom.zanussi@linux.intel.com>
>
> All var_refs are now handled uniformly and there's no reason to treat
> the synth_refs in a special way now, so remove them and associated
> functions.
>
> Link: http://lkml.kernel.org/r/b4d3470526b8f0426dcec125399dad9ad9b8589d.1545161087.git.tom.zanussi@linux.intel.com
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
> Reviewed-by: Masami Hiramatsu <mhiramat@kernel.org>
> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> Signed-off-by: George Guo <guodongtai@kylinos.cn>
> ---
> kernel/trace/trace_events_hist.c | 18 ------------------
> 1 file changed, 18 deletions(-)
What is the git commit id of this change in Linus's tree? Always
include that please.
Can you fix up and resend the series?
thanks,
greg k-h
next prev parent reply other threads:[~2024-04-19 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 1:54 [PATCH 4.19.y v5 0/2] Double-free bug discovery on testing trigger-field-variable-support.tc George Guo
2024-04-16 1:54 ` [PATCH 4.19.y v5 1/2] tracing: Remove hist trigger synth_var_refs George Guo
2024-04-19 11:18 ` Greg KH [this message]
2024-04-16 1:54 ` [PATCH 4.19.y v5 2/2] tracing: Use var_refs[] for hist trigger reference checking George Guo
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=2024041946-primarily-panning-8fd1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dongtai.guo@linux.dev \
--cc=guodongtai@kylinos.cn \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=tom.zanussi@linux.intel.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.