From: Leo Yan <leo.yan@arm.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-perf-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 0/4] perf arm_spe: Extend SIMD operations
Date: Fri, 10 Apr 2026 08:34:51 +0100 [thread overview]
Message-ID: <20260410073451.GY356832@e132581.arm.com> (raw)
In-Reply-To: <adiGR-A-N1tMzxTE@google.com>
On Thu, Apr 09, 2026 at 10:10:31PM -0700, Namhyung Kim wrote:
> On Wed, Apr 08, 2026 at 10:42:30AM +0100, Leo Yan wrote:
> > This series extends SIMD flag for Arm SPE and updated the document.
> >
> > Since I failed to get perf core maintainer's review for uAPI header
> > updating for data source fields (since last year's Sepetember), this
> > series I dropped uAPI changes and sent only SIMD flag changes, hope
> > it is easier for perf tool maintainer's picking up.
> >
> > Anyway, uAPI patches will be sent out separately.
> >
> > This version is rebased onto the latest perf-tools-next branch.
>
> Unfortunately it doesn't apply due to a recent change. Can you please
> rebase it once again?
Sure, I will send out a new version. Thanks for taking care of this!
prev parent reply other threads:[~2026-04-10 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 9:42 [PATCH v5 0/4] perf arm_spe: Extend SIMD operations Leo Yan
2026-04-08 9:42 ` [PATCH v5 1/4] perf sort: Support sort ASE and SME Leo Yan
2026-04-08 9:42 ` [PATCH v5 2/4] perf sort: Sort disabled and full predicated flags Leo Yan
2026-04-08 9:42 ` [PATCH v5 3/4] perf report: Update document for SIMD flags Leo Yan
2026-04-08 9:42 ` [PATCH v5 4/4] perf arm_spe: Improve SIMD flags setting Leo Yan
2026-04-10 5:06 ` [PATCH v5 0/4] perf arm_spe: Extend SIMD operations Namhyung Kim
2026-04-10 5:10 ` Namhyung Kim
2026-04-10 7:34 ` Leo Yan [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=20260410073451.GY356832@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.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