From: Namhyung Kim <namhyung@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: James Clark <james.clark@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, suzuki.poulose@arm.com,
will@kernel.org, mark.rutland@arm.com,
Catalin Marinas <catalin.marinas@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 3/3] Documentation: arm64: Document the PMU event counting threshold feature
Date: Wed, 29 Nov 2023 16:26:29 -0800 [thread overview]
Message-ID: <CAM9d7cjvJy21G4E04_eN8wJyOSwped-q60z8hLjWZ+N8n4Ua3w@mail.gmail.com> (raw)
In-Reply-To: <6bb84dec-42de-431a-b2e2-ebb532e0375e@arm.com>
Hello,
On Sun, Nov 26, 2023 at 9:50 PM Anshuman Khandual
<anshuman.khandual@arm.com> wrote:
>
>
>
> On 11/24/23 15:58, James Clark wrote:
> > Add documentation for the new Perf event open parameters and
> > the threshold_max capability file.
> >
> > Signed-off-by: James Clark <james.clark@arm.com>
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
next prev parent reply other threads:[~2023-11-30 0:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 10:28 [PATCH v6 0/3] arm64: perf: Add support for event counting threshold James Clark
2023-11-24 10:28 ` [PATCH v6 1/3] arm64: perf: Include threshold control fields in PMEVTYPER mask James Clark
2023-11-24 10:28 ` [PATCH v6 2/3] arm64: perf: Add support for event counting threshold James Clark
2023-11-27 5:32 ` Anshuman Khandual
2023-11-27 10:24 ` James Clark
2023-11-30 6:21 ` Anshuman Khandual
2023-12-05 13:14 ` Will Deacon
2023-12-05 15:05 ` James Clark
2023-12-05 16:34 ` Suzuki K Poulose
2023-11-24 10:28 ` [PATCH v6 3/3] Documentation: arm64: Document the PMU event counting threshold feature James Clark
2023-11-27 5:50 ` Anshuman Khandual
2023-11-30 0:26 ` Namhyung Kim [this message]
2023-11-30 10:36 ` Suzuki K Poulose
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=CAM9d7cjvJy21G4E04_eN8wJyOSwped-q60z8hLjWZ+N8n4Ua3w@mail.gmail.com \
--to=namhyung@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=james.clark@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).