The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andreas Schwab <schwab@suse.de>,
	jianchunfu <jianchunfu@cmss.chinamobile.com>
Subject: Re: [GIT PULL] rtla: Updates for 5.20/6.0
Date: Sat, 6 Aug 2022 14:06:10 -0400 (EDT)	[thread overview]
Message-ID: <995effeb-2b1f-ef57-5f71-846dee8da023@redhat.com> (raw)
In-Reply-To: <CAHk-=wj3zXDnXUHb-EKAkk74GUixO8ojUZMt-rkTsXSxALpi_g@mail.gmail.com>



On Sat, 6 Aug 2022, Linus Torvalds wrote:

> On Sat, Aug 6, 2022 at 6:01 AM Daniel Bristot de Oliveira
> <bristot@kernel.org> wrote:
> >
> > Yes, I will do that. I will also do minimal fedora install and cross-check this further.
> 
> For extra bonus points, if you can state all missing packages in one
> go (instead of "oops you don't have Xyz" followed by install of Xyz,
> followed by "Oops, now you don't have Abc") that would be nice too.
> 
> But at this point the fundamental problem with incomprehensible error
> messages is long gone, so it's not a big deal and not worth lots of
> effort. More of a "if it's easy enough.."
> 
>                 Linus
> 

Daniel, if it helps,
for Fedora I've got

Build Time Requires
-------------------
BuildRequires: gcc 
BuildRequires: python3-docutils
BuildRequires: procps-ng-devel
BuildRequires: libtraceevent-devel
BuildRequires: libtracefs-devel

Run Time Requires
----------------
Requires: procps-ng       
Requires: libtraceevent
Requires: libtracefs

John Kacur


  reply	other threads:[~2022-08-06 18:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 14:49 [GIT PULL] rtla: Updates for 5.20/6.0 Steven Rostedt
2022-08-05 16:40 ` Linus Torvalds
2022-08-05 16:47   ` Steven Rostedt
2022-08-06 13:01     ` Daniel Bristot de Oliveira
2022-08-06 15:52       ` Linus Torvalds
2022-08-06 18:06         ` John Kacur [this message]
2022-08-06 18:22         ` Steven Rostedt
2022-08-06 18:24           ` Linus Torvalds
2022-08-06 18:51             ` Steven Rostedt
2022-08-06 19:05               ` Linus Torvalds
2022-08-06 19:23                 ` Steven Rostedt
2022-08-06 18:45           ` Steven Rostedt
2022-08-06 18:47             ` Steven Rostedt
2022-08-05 17:42 ` 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=995effeb-2b1f-ef57-5f71-846dee8da023@redhat.com \
    --to=jkacur@redhat.com \
    --cc=bristot@kernel.org \
    --cc=jianchunfu@cmss.chinamobile.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=schwab@suse.de \
    --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