From: Ingo Molnar <mingo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [GIT PULL] Performance events changes for v6.12
Date: Thu, 19 Sep 2024 11:53:20 +0200 [thread overview]
Message-ID: <Zuv0kA-um9ZT-Tjd@gmail.com> (raw)
In-Reply-To: <20240919082624.05ca5fd6@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> On Wed, 18 Sep 2024 14:45:39 +0200 Ingo Molnar <mingo@kernel.org> wrote:
> >
> > Please pull the latest perf/core Git tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-core-2024-09-18
> >
> > # HEAD: 5e645f31139183ac9a282238da18ca6bbc1c6f4a Merge branch 'perf/urgent' into perf/core, to pick up fixes
>
> > perf: Generic hotplug support for a PMU with a scope
>
> This commit introduces a (reported) build warning in some configurations:
>
> https://lore.kernel.org/all/20240911153854.240bbc1f@canb.auug.org.au
>
> That turns into a build failure for some configurations :-(
Thanks: I've queued up the fix for this ARM warning in perf/urgent and will
get it to Linus later today.
Ingo
next prev parent reply other threads:[~2024-09-19 9:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 12:45 [GIT PULL] Performance events changes for v6.12 Ingo Molnar
2024-09-18 13:00 ` Linus Torvalds
[not found] ` <ZuvhwjNgDmpmReUl@gmail.com>
2024-09-19 8:42 ` Linus Torvalds
2024-09-19 8:48 ` Ingo Molnar
2024-09-19 8:50 ` Linus Torvalds
2024-09-18 13:12 ` Linus Torvalds
2024-09-19 8:42 ` Ingo Molnar
2024-09-18 14:00 ` pr-tracker-bot
2024-09-18 22:26 ` Stephen Rothwell
2024-09-19 9:53 ` Ingo Molnar [this message]
2024-09-19 10:42 ` Stephen Rothwell
2024-09-21 22:39 ` Linus Torvalds
2024-09-22 19:50 ` Linus Torvalds
2024-09-23 15:27 ` Ingo Molnar
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=Zuv0kA-um9ZT-Tjd@gmail.com \
--to=mingo@kernel.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--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 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).