From: Jani Nikula <jani.nikula@linux.intel.com>
To: Denis Arefev <arefev@swemel.ru>
Cc: ldv-project@linuxtesting.org, trufanov@swemel.ru,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, vfh@swemel.ru,
Daniel Vetter <daniel@ffwll.ch>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH 3/3] i915-pmu: Add extra check NULL
Date: Tue, 16 Aug 2022 13:03:24 +0300 [thread overview]
Message-ID: <878rnoqzdf.fsf@intel.com> (raw)
In-Reply-To: <20220816092525.37670-1-arefev@swemel.ru>
On Tue, 16 Aug 2022, Denis Arefev <arefev@swemel.ru> wrote:
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
The subject prefix should be something along the lines of
"drm/i915/pmu".
The subject is misleading; there are no functional changes here, just
whitespace changes. I'm guessing you intended to send something else?
Finally, the commit message is primarily for describing why the change
is being made, not to advertize organizations or tools.
BR,
Jani.
>
> Signed-off-by: Denis Arefev <arefev@swemel.ru>
> ---
> drivers/gpu/drm/i915/i915_pmu.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_pmu.c b/drivers/gpu/drm/i915/i915_pmu.c
> index 34a7f0ef1f67..33db49ffac3d 100644
> --- a/drivers/gpu/drm/i915/i915_pmu.c
> +++ b/drivers/gpu/drm/i915/i915_pmu.c
> @@ -704,8 +704,7 @@ static void i915_pmu_disable(struct perf_event *event)
> * Decrement the reference count and clear the enabled
> * bitmask when the last listener on an event goes away.
> */
> - if(engine != NULL)
> - {
> + if (engine != NULL) {
> if (--engine->pmu.enable_count[sample] == 0)
> engine->pmu.enable &= ~BIT(sample);
> }
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2022-08-16 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 9:25 [Intel-gfx] [PATCH 3/3] i915-pmu: Add extra check NULL Denis Arefev
2022-08-16 10:03 ` Jani Nikula [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=878rnoqzdf.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=arefev@swemel.ru \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ldv-project@linuxtesting.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=trufanov@swemel.ru \
--cc=vfh@swemel.ru \
/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