From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Zide Chen <zide.chen@intel.com>,
Falcon Thomas <thomas.falcon@intel.com>,
Dapeng Mi <dapeng1.mi@intel.com>,
Xudong Hao <xudong.hao@intel.com>
Subject: Re: [PATCH 1/2] perf alsr: Add missing SIMD handling in aslr_tool__process_sample()
Date: Tue, 22 Sep 2026 14:50:35 +0200 [thread overview]
Message-ID: <arJ5mwKTBuludevg@x2> (raw)
In-Reply-To: <CAP-5=fWTRPmPTkzd98hCEfh6LUTrRTNHZ2dS4nUDyQBuU8oSzg@mail.gmail.com>
On Mon, Sep 21, 2026 at 09:22:11AM -0700, Ian Rogers wrote:
> On Mon, Sep 21, 2026 at 9:21 AM Ian Rogers <irogers@google.com> wrote:
> >
> > On Sun, Sep 20, 2026 at 11:42 PM Mi, Dapeng <dapeng1.mi@linux.intel.com> wrote:
> > >
> > > Kindly ping ...
> > >
> > > @Arnaldo, @Namhyung, @Ian, not sure if you have bandwidth to review this
> > > small patchset which fixes the Sashiko found minor issues for the "Perf
> > > tools: Support eGPRs/SSP/SIMD registers sampling" patchset?
> > >
> > > If possible, it's better to be queued in this cycle, then we don't need
> > > extra backporting. Thanks.
> >
> > Reviewed-by: Ian Rogers <irogers@google.com>
>
> Oh, another nit: there's a typo in the commit message subject: s/alsr/aslr/g.
Fixed.
Thanks, applied to perf-tools-next, for v7.4.
- Arnaldo
next prev parent reply other threads:[~2026-09-22 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 9:11 Dapeng Mi
2026-09-15 9:11 ` [PATCH 2/2] perf util: Explicitly include required headers Dapeng Mi
2026-09-21 16:23 ` Ian Rogers
2026-09-21 6:42 ` [PATCH 1/2] perf alsr: Add missing SIMD handling in aslr_tool__process_sample() Mi, Dapeng
2026-09-21 16:21 ` Ian Rogers
2026-09-21 16:22 ` Ian Rogers
2026-09-22 0:31 ` Mi, Dapeng
2026-09-22 12:50 ` Arnaldo Carvalho de Melo [this message]
2026-09-22 0:30 ` 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=arJ5mwKTBuludevg@x2 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dapeng1.mi@intel.com \
--cc=dapeng1.mi@linux.intel.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=thomas.falcon@intel.com \
--cc=xudong.hao@intel.com \
--cc=zide.chen@intel.com \
/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
all inboxes | Powered by JetHome®