From: Steven Rostedt <rostedt@goodmis.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: dvyukov@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] tracing: hist trigger KASAN fixes
Date: Tue, 2 Aug 2016 15:11:12 -0400 [thread overview]
Message-ID: <20160802151112.2aed0bcc@gandalf.local.home> (raw)
In-Reply-To: <57A0ED09.1050809@linux.intel.com>
On Tue, 02 Aug 2016 13:57:13 -0500
Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
> Hi Steve,
>
> It looks like these two patches were never merged..
>
Because they got buried in my INBOX. :-(
-- Steve
prev parent reply other threads:[~2016-08-02 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 0:55 [PATCH 0/2] tracing: hist trigger KASAN fixes Tom Zanussi
2016-06-30 0:55 ` [PATCH 1/2] tracing: Fix use-after-free in hist_unreg_all/hist_enable_unreg_all Tom Zanussi
2016-06-30 0:56 ` [PATCH 2/2] tracing: Fix use-after-free in hist_register_trigger() Tom Zanussi
2016-08-02 18:57 ` [PATCH 0/2] tracing: hist trigger KASAN fixes Tom Zanussi
2016-08-02 19:11 ` 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=20160802151112.2aed0bcc@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=dvyukov@google.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).