From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/pmu: Remove i915_pmu_event_event_idx()
Date: Mon, 13 Jan 2025 10:42:52 -0800 [thread overview]
Message-ID: <85zfjuees3.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20250113183329.3138138-1-lucas.demarchi@intel.com>
On Mon, 13 Jan 2025 10:33:29 -0800, Lucas De Marchi wrote:
>
> perf event already has a default function that returns 0, no need to
> override with the same thing.
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> drivers/gpu/drm/i915/i915_pmu.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_pmu.c b/drivers/gpu/drm/i915/i915_pmu.c
> index e55db036be1bb..2eecd42f61ba1 100644
> --- a/drivers/gpu/drm/i915/i915_pmu.c
> +++ b/drivers/gpu/drm/i915/i915_pmu.c
> @@ -891,11 +891,6 @@ static void i915_pmu_event_del(struct perf_event *event, int flags)
> i915_pmu_event_stop(event, PERF_EF_UPDATE);
> }
>
> -static int i915_pmu_event_event_idx(struct perf_event *event)
> -{
> - return 0;
> -}
> -
> struct i915_str_attribute {
> struct device_attribute attr;
> const char *str;
> @@ -1301,7 +1296,6 @@ void i915_pmu_register(struct drm_i915_private *i915)
> pmu->base.start = i915_pmu_event_start;
> pmu->base.stop = i915_pmu_event_stop;
> pmu->base.read = i915_pmu_event_read;
> - pmu->base.event_idx = i915_pmu_event_event_idx;
>
> ret = perf_pmu_register(&pmu->base, pmu->name, -1);
> if (ret)
> --
> 2.48.0
>
next prev parent reply other threads:[~2025-01-13 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 18:33 [PATCH] drm/i915/pmu: Remove i915_pmu_event_event_idx() Lucas De Marchi
2025-01-13 18:42 ` Dixit, Ashutosh [this message]
2025-01-13 20:47 ` ✓ i915.CI.BAT: success for " Patchwork
2025-01-15 6:47 ` ✗ i915.CI.Full: failure " Patchwork
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=85zfjuees3.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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