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>
Subject: Re: [PATCH 4.19.y v4 1/2] tracing: Remove hist trigger synth_var_refs
Date: Mon, 15 Apr 2024 13:17:05 +0200 [thread overview]
Message-ID: <2024041533-clang-circle-f651@gregkh> (raw)
In-Reply-To: <20240412093041.2334396-2-dongtai.guo@linux.dev>
On Fri, Apr 12, 2024 at 05:30:40PM +0800, George Guo wrote:
> From: Tom Zanussi <tom.zanussi@linux.intel.com>
>
> commit 912201345f7c39e6b0ac283207be2b6641fa47b9 upstream.
>
> 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>
You can not send patches on without also signing off on them, right?
Please fix up when you resend this.
thanks,
greg k-h
next prev parent reply other threads:[~2024-04-15 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 9:30 [PATCH 4.19.y v4 0/2] Double-free bug discovery on testing trigger-field-variable-support.tc George Guo
2024-04-12 9:30 ` [PATCH 4.19.y v4 1/2] tracing: Remove hist trigger synth_var_refs George Guo
2024-04-15 11:17 ` Greg KH [this message]
2024-04-12 9:30 ` [PATCH 4.19.y v4 2/2] tracing: Use var_refs[] for hist trigger reference checking George Guo
2024-04-15 11:17 ` Greg KH
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=2024041533-clang-circle-f651@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dongtai.guo@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox