All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Peter Ziljstra <peterz@infradead.org>
Cc: Andrii Nakryiko <andrii.nakryiko@gmail.com>,
	Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Linux trace kernel <linux-trace-kernel@vger.kernel.org>,
	bpf <bpf@vger.kernel.org>, Oleg Nesterov <oleg@redhat.com>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Liao Chang <liaochang1@huawei.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>,
	"linux-perf-use." <linux-perf-users@vger.kernel.org>,
	Kernel Team <kernel-team@meta.com>
Subject: Re: The state of uprobes work and logistics
Date: Thu, 24 Oct 2024 19:38:43 +0200	[thread overview]
Message-ID: <ZxqGIyvIQMXCyApJ@krava> (raw)
In-Reply-To: <CAEf4BzacLW14OmuW1nV4s=cMcSqcrSAO2Y_0XY3jT2efGNfmuw@mail.gmail.com>

On Wed, Oct 23, 2024 at 10:38:54AM -0700, Andrii Nakryiko wrote:

SNIP

> > Peter, do you mind applying those two and creating a stable tag for
> > bpf-next to pull? We'll apply the rest of Jiri's series to
> > bpf-next/master.
> 
> Jiri has reposted patches this time CC'ing Peter, heh :), it would be
> great to apply those two patches and get a stable tag. This is

hi,
any news on this one? I saw the patches in peterz/perf/core,
but I think we still need the stable tag for bpf-next/master

thanks,
jirka


> blocking the landing of uprobe sessions in bpf-next and also my
> remaining patches will be based on top of Jiri's uprobe changes, most
> probably. Peter, please take another look, thank you.

SNIP

  reply	other threads:[~2024-10-24 17:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16 19:35 The state of uprobes work and logistics Andrii Nakryiko
2024-10-18  7:36 ` Peter Zijlstra
2024-10-18 20:27   ` Jiri Olsa
2024-10-23 17:38 ` Andrii Nakryiko
2024-10-24 17:38   ` Jiri Olsa [this message]
2024-10-30  9:42 ` Jiri Olsa
2024-11-06  2:11   ` Andrii Nakryiko
2024-11-06 10:46     ` Peter Zijlstra
2024-11-06 11:05       ` Peter Zijlstra
2024-11-06 16:15         ` Andrii Nakryiko

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=ZxqGIyvIQMXCyApJ@krava \
    --to=olsajiri@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@meta.com \
    --cc=liaochang1@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.