linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCH] perf/x86/intel: Fix and clean up intel_pmu_drain_arch_pebs() type use
Date: Wed, 12 Nov 2025 12:14:04 +0100	[thread overview]
Message-ID: <aRRr_O9Enzkb5B5d@gmail.com> (raw)
In-Reply-To: <d3d49960-b7b6-4270-961e-9895cfdff1be@linux.intel.com>


* Mi, Dapeng <dapeng1.mi@linux.intel.com> wrote:

> BTW, the offensive commit should be the below one instead of '2721e8da2de7
> ("perf/x86/intel: Allocate arch-PEBS buffer and initialize PEBS_BASE MSR") '.
> 
> d21954c8a0ff ("perf/x86/intel: Process arch-PEBS records or record fragments")

Indeed, this is the one that introduced it - I fixed 
the changelog and updated the tags.

Thanks,

	Ingo

  reply	other threads:[~2025-11-12 11:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12  4:42 linux-next: build failure after merge of the tip tree Stephen Rothwell
2025-11-12  5:20 ` Mi, Dapeng
2025-11-12 10:09   ` [PATCH] perf/x86/intel: Fix and clean up intel_pmu_drain_arch_pebs() type use Ingo Molnar
2025-11-12 10:36     ` Mi, Dapeng
2025-11-12 11:14       ` Ingo Molnar [this message]
2025-11-12  9:39 ` linux-next: build failure after merge of the tip tree Peter Zijlstra
2025-11-12 10:45   ` Stephen Rothwell
2025-11-12 10:48     ` Peter Zijlstra
2025-11-12 12:31       ` Mi, Dapeng

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=aRRr_O9Enzkb5B5d@gmail.com \
    --to=mingo@kernel.org \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    /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).