Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 11 Dec 2018 12:46:12 -0500
From:   Steven Rostedt <rostedt@goodmis.org>
To:     Tom Zanussi <tom.zanussi@linux.intel.com>
Cc:     linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
        Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/2] tracing: Fix a couple of memory leaks in the event
 trigger code
Message-ID: <20181211124612.58920ceb@gandalf.local.home>
In-Reply-To: <1913c8d0be777a59d59135c067abf270b0594c63.camel@linux.intel.com>
References: <20181210204126.603121253@goodmis.org>
        <1913c8d0be777a59d59135c067abf270b0594c63.camel@linux.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, 11 Dec 2018 10:40:19 -0600
Tom Zanussi <tom.zanussi@linux.intel.com> wrote:

> Hi Steve,
> 
> On Mon, 2018-12-10 at 15:41 -0500, Steven Rostedt wrote:
> > Tom,
> > 
> > While testing other changes, kmemleak pointed out a few leaks in the
> > trigger code. Can you take a look at them and give me a Reviewed-by
> > or Ack.
> > 
> > Thanks!
> > 
> > -- Steve
> > 
> > 
> > Steven Rostedt (VMware) (2):
> >       tracing: Fix memory leak in create_filter()
> >       tracing: Fix memory leak in set_trigger_filter()
> >   
> 
> Sure, these look fine to me.
> 
> Reviewed-by: Tom Zanussi <tom.zanussi@linux.intel.com>
> 
>

Thanks a lot Tom!

-- Steve