From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH 0/4 v4] perf: Fix leaked sigtrap events
Date: Tue, 25 Jun 2024 10:43:05 +0200 [thread overview]
Message-ID: <20240625084305.GV31592@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20240621091601.18227-1-frederic@kernel.org>
On Fri, Jun 21, 2024 at 11:15:57AM +0200, Frederic Weisbecker wrote:
> Hi,
>
> This is essentially a resend to remind the patchset on people's pile,
> using a small typo fix on patch 3 (thanks Sebastian) as an excuse.
Poke worked -- I remember going through this a while ago and only having
small niggles. So this one must be good :-)
I've queued the thing for perf/urgent.
prev parent reply other threads:[~2024-06-25 8:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 9:15 Frederic Weisbecker
2024-06-21 9:15 ` [PATCH 1/4] task_work: s/task_work_cancel()/task_work_cancel_func()/ Frederic Weisbecker
2024-07-01 7:14 ` [tip: perf/urgent] " tip-bot2 for Frederic Weisbecker
2024-07-09 11:42 ` [tip: perf/core] " tip-bot2 for Frederic Weisbecker
2024-06-21 9:15 ` [PATCH 2/4] task_work: Introduce task_work_cancel() again Frederic Weisbecker
2024-07-01 7:14 ` [tip: perf/urgent] " tip-bot2 for Frederic Weisbecker
2024-07-09 11:42 ` [tip: perf/core] " tip-bot2 for Frederic Weisbecker
2024-06-21 9:16 ` [PATCH 3/4] perf: Fix event leak upon exit Frederic Weisbecker
2024-07-01 7:14 ` [tip: perf/urgent] " tip-bot2 for Frederic Weisbecker
2024-07-09 11:42 ` [tip: perf/core] " tip-bot2 for Frederic Weisbecker
2024-06-21 9:16 ` [PATCH 4/4] perf: Fix event leak upon exec and file release Frederic Weisbecker
2024-07-01 7:14 ` [tip: perf/urgent] " tip-bot2 for Frederic Weisbecker
2024-07-09 11:41 ` [tip: perf/core] " tip-bot2 for Frederic Weisbecker
2024-06-25 8:43 ` Peter Zijlstra [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=20240625084305.GV31592@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@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
Powered by JetHome