Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 24 May 2022 21:34:27 -0400
From:   Steven Rostedt <rostedt@goodmis.org>
To:     Wang ShaoBo <bobo.shaobowang@huawei.com>
Cc:     <cj.chengjian@huawei.com>, <linux-kernel@vger.kernel.org>,
        <liwei391@huawei.com>, <mhiramat@kernel.org>, <acme@redhat.com>,
        <yuehaibing@huawei.com>
Subject: Re: [PATCH 0/2] tools libtraceevent fixes
Message-ID: <20220524213427.1b0b837c@gandalf.local.home>
In-Reply-To: <20220513023308.2400381-1-bobo.shaobowang@huawei.com>
References: <20220513023308.2400381-1-bobo.shaobowang@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 13 May 2022 10:33:06 +0800
Wang ShaoBo <bobo.shaobowang@huawei.com> wrote:

> tools libtraceevent fixes
> 
> Wang ShaoBo (2):
>   libtraceevent: fix memleak in make_bprint_args()
>   libtraceevent: fix free NULL pointer in parse_arg_add()

These fixes need to be sent to linux-trace-devel@vger.kernel.org, and
applied against libtraceevent:

  https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/

Arnaldo,

libtraceevent is now in most distros. Can we now deprecate the version in
the kernel as it is no longer actively maintained?

-- Steve


> 
>  tools/lib/traceevent/event-parse.c | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
>