From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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: Mon, 23 Sep 2024 17:27:34 +0200 [thread overview]
Message-ID: <ZvGI5lcRAOnp2rTW@gmail.com> (raw)
In-Reply-To: <CAHk-=wjjrLPDVMu2Bj+01XmZF=puP0nKXbLzC40fe_enGDdcBg@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sat, 21 Sept 2024 at 15:39, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > On Thu, 19 Sept 2024 at 02:53, Ingo Molnar <mingo@kernel.org> wrote:
> > >
> > > Thanks: I've queued up the fix for this ARM warning in perf/urgent
> > > and will get it to Linus later today.
> >
> > So this apparently never happened.
Sorry about that, was sick for a few days.
> > I'm back home now, and so I now do my arm64 builds too, and it is
> > indeed failing.
>
> In case people didn't notice - in order to now do my now usual full
> builds I just took the fix directly (commit 673a5009cf2f: "perf: Fix
> topology_sibling_cpumask check warning on ARM").
Looks good, thank you!
Ingo
prev parent reply other threads:[~2024-09-23 15:27 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
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 [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=ZvGI5lcRAOnp2rTW@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 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.