From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] tracing/rtla: Updates to the RTLA tool
Date: Wed, 23 Mar 2022 20:32:59 +0100 [thread overview]
Message-ID: <21ebdc8c-ddf8-cd0a-b93c-5d5dd74a9a84@kernel.org> (raw)
In-Reply-To: <CAHk-=whxmA86E=csNv76DuxX_wYsg8mW15oUs3XTabu2Yc80yw@mail.gmail.com>
On 3/23/22 19:15, Linus Torvalds wrote:
> On Mon, Mar 21, 2022 at 7:30 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>>
>> I'm sending this as a separate pull request from my normal tracing tree, as
>> it had dependencies to commits in your tree but not in my development
>> branch. As it only affects the tools/ directory, I kept it separate as it
>> has no changes to the kernel itself.
>
> Yes, please keep the tooling updates separate from the kernel ones,
> the way we now for some time have for the perf tooling too.
>
> That said, mentioning the perf tools, I wish the tracing tools would
> do a bit more package checking and helpful error messages too, rather
> than just fail with
>
> fatal error: tracefs.h: No such file or directory
>
> when (presumably) libtracefs and friends are needed.
>
> Hmm?
Yes, we need to improve the Makefile.
It depends on procps-ng-devel and python3-docutils packages and the latest
libtracefs (1.3) and libtraceevent (1.5). There is info about it in the README,
but we definitely need to improve the Makefile... I will prioritize that.
-- Daniel
> Linus
next prev parent reply other threads:[~2022-03-23 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 14:30 Steven Rostedt
2022-03-23 18:15 ` Linus Torvalds
2022-03-23 19:32 ` Daniel Bristot de Oliveira [this message]
2022-03-23 19:43 ` Steven Rostedt
2022-03-23 19:52 ` Daniel Bristot de Oliveira
2022-03-23 19:26 ` pr-tracker-bot
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=21ebdc8c-ddf8-cd0a-b93c-5d5dd74a9a84@kernel.org \
--to=bristot@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®