From: Jonathan Corbet <corbet@lwn.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Tomas Glozar <tglozar@redhat.com>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, John Kacur <jkacur@redhat.com>
Subject: Re: [PATCH 4/4] Documentation/rtla: Include BPF sample collection
Date: Mon, 14 Apr 2025 10:43:42 -0600 [thread overview]
Message-ID: <875xj6ae2p.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250324195359.7e593f2f@gandalf.local.home>
Steven Rostedt <rostedt@goodmis.org> writes:
> On Mon, 17 Mar 2025 16:47:41 -0600
> Jonathan Corbet <corbet@lwn.net> wrote:
>
>> What is the intended path to get this one upstream; should I take it?
>
> Hi Jon,
>
> Yes, can you take this through your tree?
>
> You can add:
>
> Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
...and I have finally done that ...
Thanks,
jon
next prev parent reply other threads:[~2025-04-14 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 11:49 [PATCH 0/4] Documentation/rtla: Cover BPF sample collection Tomas Glozar
2025-03-11 11:49 ` [PATCH 1/4] Documentation/rtla: Fix duplicate text about timerlat tracer Tomas Glozar
2025-03-11 11:49 ` [PATCH 2/4] Documentation/rtla: Fix typo in rtla-timerlat.rst Tomas Glozar
2025-03-11 11:49 ` [PATCH 3/4] Documentation/rtla: Fix typo in common_timerlat_description.rst Tomas Glozar
2025-03-11 11:49 ` [PATCH 4/4] Documentation/rtla: Include BPF sample collection Tomas Glozar
2025-03-11 13:07 ` Luis Claudio R. Goncalves
2025-03-11 13:20 ` Tomas Glozar
2025-03-17 22:47 ` Jonathan Corbet
2025-03-24 23:53 ` Steven Rostedt
2025-04-14 16:43 ` Jonathan Corbet [this message]
2025-03-11 13:09 ` [PATCH 0/4] Documentation/rtla: Cover " Luis Claudio R. Goncalves
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=875xj6ae2p.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=jkacur@redhat.com \
--cc=lgoncalv@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglozar@redhat.com \
/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