From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Gowthami Thiagarajan <gthiagarajan@marvell.com>
Cc: <will@kernel.org>, <mark.rutland@arm.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <gcherian@marvell.com>,
<bbhushan2@marvell.com>, <sgoutham@marvell.com>
Subject: Re: [PATCH v8 2/6] perf/marvell: Refactor to extract platform specific ops - no functional change
Date: Tue, 24 Sep 2024 17:19:34 +0100 [thread overview]
Message-ID: <20240924171934.00002882@Huawei.com> (raw)
In-Reply-To: <20240919074717.3276854-3-gthiagarajan@marvell.com>
On Thu, 19 Sep 2024 13:17:13 +0530
Gowthami Thiagarajan <gthiagarajan@marvell.com> wrote:
> This commit introduces a refactor to the Marvell DDR pmu driver,
> specifically targeting the extraction of ops
> (referred to as "pmu ops") from the existing driver.
>
> Signed-off-by: Gowthami Thiagarajan <gthiagarajan@marvell.com>
Looks fine to me.
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
next prev parent reply other threads:[~2024-09-24 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 7:47 [PATCH v8 0/6] Marvell Odyssey uncore performance monitor support Gowthami Thiagarajan
2024-09-19 7:47 ` [PATCH v8 1/6] perf/marvell: Refactor to extract platform data - no functional change Gowthami Thiagarajan
2024-09-24 16:18 ` Jonathan Cameron
2024-09-19 7:47 ` [PATCH v8 2/6] perf/marvell: Refactor to extract platform specific ops " Gowthami Thiagarajan
2024-09-24 16:19 ` Jonathan Cameron [this message]
2024-09-19 7:47 ` [PATCH v8 3/6] perf/marvell: Refactor to add version " Gowthami Thiagarajan
2024-09-24 16:23 ` Jonathan Cameron
2024-09-19 7:47 ` [PATCH v8 4/6] perf/marvell: Odyssey DDR Performance monitor support Gowthami Thiagarajan
2024-09-24 16:28 ` Jonathan Cameron
2024-09-19 7:47 ` [PATCH v8 5/6] perf/marvell : Refactor to extract platform data - no functional change Gowthami Thiagarajan
2024-09-19 7:47 ` [PATCH v8 6/6] perf/marvell : Odyssey LLC-TAD performance monitor support Gowthami Thiagarajan
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=20240924171934.00002882@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=bbhushan2@marvell.com \
--cc=gcherian@marvell.com \
--cc=gthiagarajan@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sgoutham@marvell.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