From: Chen Pei <cp0613@linux.alibaba.com>
To: acme@kernel.org
Cc: adrian.hunter@intel.com, alexander.shishkin@linux.intel.com,
anup@brainfault.org, david.laight.linux@gmail.com,
guoren@kernel.org, irogers@google.com, james.clark@linaro.org,
john.g.garry@oracle.com, jolsa@kernel.org, leo.yan@linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-riscv@lists.infradead.org, mark.rutland@arm.com,
mike.leach@arm.com, mingo@redhat.com, namhyung@kernel.org,
palmer@dabbelt.com, peterz@infradead.org, pjw@kernel.org,
will@kernel.org
Subject: Re: [PATCH v3 0/2] perf riscv: Implement rdtsc()
Date: Thu, 5 Nov 2026 17:02:57 +0800 [thread overview]
Message-ID: <20261105090300.2889-1-cp0613@linux.alibaba.com> (raw)
In-Reply-To: <20261009032715.2841-1-cp0613@linux.alibaba.com>
On Fri, Oct 09, 2026 at 11:27:13AM +0800, Chen Pei wrote:
> [PATCH v3 0/2] perf riscv: Implement rdtsc()
Gentle ping on this series.
Is there anything else you need from me to get it queued for the next
perf-tools cycle? If you would rather see it resent on a newer base,
or want a change I have not thought of, say the word and I will do that.
Best regards,
Chen
prev parent reply other threads:[~2026-11-05 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 3:27 Chen Pei
2026-10-09 3:27 ` [PATCH v3 1/2] " Chen Pei
2026-10-09 3:27 ` [PATCH v3 2/2] perf tsc: Declare TSC support from the build system Chen Pei
2026-11-05 9:02 ` Chen Pei [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=20261105090300.2889-1-cp0613@linux.alibaba.com \
--to=cp0613@linux.alibaba.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anup@brainfault.org \
--cc=david.laight.linux@gmail.com \
--cc=guoren@kernel.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pjw@kernel.org \
--cc=will@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
all inboxes | Powered by JetHome®