From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [GIT PULL] perf events fix
Date: Sun, 1 Feb 2026 12:31:24 +0100 [thread overview]
Message-ID: <20260201113124.GA2995752@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <aX8T5mj8ZJ-FAJ0H@gmail.com>
On Sun, Feb 01, 2026 at 09:50:46AM +0100, Ingo Molnar wrote:
> Linus,
>
> Please pull the latest perf/urgent Git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-2026-02-01
>
> for you to fetch changes up to 76ed27608f7dd235b727ebbb12163438c2fbb617:
>
> Fix a race in the user-callchains code.
>
> Thanks,
>
> Ingo
>
So both this and the sched thing are *really* fresh, I stuck them in
late Friday and left you a message that they should probably go in next
week.
That said; they're not the riskiest of patches, but would'be been nice
to still wait a bit.
next prev parent reply other threads:[~2026-02-01 11:31 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 8:50 [GIT PULL] perf events fix Ingo Molnar
2026-02-01 11:31 ` Peter Zijlstra [this message]
2026-02-01 18:26 ` Linus Torvalds
2026-02-01 20:04 ` Peter Zijlstra
2026-02-01 20:08 ` Linus Torvalds
2026-02-01 19:46 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2026-04-05 9:45 Ingo Molnar
2026-04-05 22:33 ` pr-tracker-bot
2026-01-11 10:25 Ingo Molnar
2026-01-12 19:38 ` pr-tracker-bot
2025-11-08 13:07 Ingo Molnar
2025-11-08 17:15 ` pr-tracker-bot
2025-09-07 10:07 Ingo Molnar
2025-09-07 15:32 ` pr-tracker-bot
2025-05-17 13:26 Ingo Molnar
2025-05-17 16:27 ` pr-tracker-bot
2025-04-06 16:58 Ingo Molnar
2025-04-06 17:53 ` pr-tracker-bot
2025-03-22 20:56 Ingo Molnar
2025-03-22 21:45 ` pr-tracker-bot
2024-06-08 7:40 Ingo Molnar
2024-06-08 16:50 ` pr-tracker-bot
2024-04-14 8:25 Ingo Molnar
2024-04-14 18:48 ` pr-tracker-bot
2023-11-26 9:43 Ingo Molnar
2023-11-26 17:16 ` pr-tracker-bot
2023-10-28 10:41 Ingo Molnar
2023-10-28 18:17 ` pr-tracker-bot
2023-10-21 15:22 Ingo Molnar
2023-10-21 18:29 ` pr-tracker-bot
2023-10-14 21:58 Ingo Molnar
2023-10-14 22:49 ` pr-tracker-bot
2023-09-10 16:20 Ingo Molnar
2023-09-10 18:08 ` 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=20260201113124.GA2995752@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--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 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.