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, 10 Jan 2023 09:53:47 -0500
From:   Steven Rostedt <rostedt@goodmis.org>
To:     Daniel Wagner <dwagner@suse.de>
Cc:     Daniel Bristot de Oliveira <bristot@kernel.org>,
        linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/rtla: Explicitly list libtraceevent dependency
Message-ID: <20230110095347.3662c3ba@gandalf.local.home>
In-Reply-To: <20230110095137.18168c29@gandalf.local.home>
References: <20230110131805.16242-1-dwagner@suse.de>
        <42d1e999-79a6-94dc-cc88-77520ddce068@kernel.org>
        <20230110140814.2yz4if2e2fasnu7t@carbon.lan>
        <94fd6fb5-c87a-b02e-40bc-b2e2c99529d5@kernel.org>
        <20230110144536.knepnpxsp4mw67no@carbon.lan>
        <20230110095137.18168c29@gandalf.local.home>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 10 Jan 2023 09:51:37 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:

> There's many interfaces that require the libtraceevent header files to work
> with libtracefs. Anything that uses libtracefs must also use libtraceevent,
> as libtracefs is really just an extension of libtraceevent.

Although, I will say, since I hate the libtraceevent interface so much, I
may like to hide it via a fully functional libtracefs interface that hides
it :-)  In which case, this would be correct!

-- Steve