linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Andrii Nakryiko <andrii@kernel.org>,
	linux-trace-kernel@vger.kernel.org,  peterz@infradead.org,
	mhiramat@kernel.org, x86@kernel.org, mingo@redhat.com,
	 tglx@linutronix.de, jpoimboe@redhat.com,
	linux-kernel@vger.kernel.org,  bpf@vger.kernel.org,
	rihams@fb.com, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v5] perf,x86: avoid missing caller address in stack traces captured in uprobe
Date: Thu, 18 Jul 2024 09:45:59 -0700	[thread overview]
Message-ID: <CAEf4BzYGWLYBOYxK6YteDNu3tEkF00MBm4d1Z7twXF-SfSZXJw@mail.gmail.com> (raw)
In-Reply-To: <20240718114521.4b0220b7@rorschach.local.home>

On Thu, Jul 18, 2024 at 8:45 AM Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Thu, 18 Jul 2024 08:29:23 -0700
> Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
>
> > Ping. What's the status of this patch? Is it just waiting until after
> > the merge window, or it got lost?
>
> It's probably best to re-ping after rc1 is out. With recent events, a
> lot of us are way behind in our work.
>

I understand, will resend later, thanks for quickly getting back to me!

> Thanks,
>
> -- Steve

      reply	other threads:[~2024-07-18 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10 19:36 [PATCH v5] perf,x86: avoid missing caller address in stack traces captured in uprobe Andrii Nakryiko
2024-07-18 15:29 ` Andrii Nakryiko
2024-07-18 15:45   ` Steven Rostedt
2024-07-18 16:45     ` Andrii Nakryiko [this message]

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=CAEf4BzYGWLYBOYxK6YteDNu3tEkF00MBm4d1Z7twXF-SfSZXJw@mail.gmail.com \
    --to=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rihams@fb.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).