From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-xe@lists.freedesktop.org, Nirmoy Das <nirmoy.das@intel.com>
Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH RESEND] drm/xe/client: Check return value of xe_force_wake_get
Date: Fri, 28 Jun 2024 10:48:31 +0200 [thread overview]
Message-ID: <2fca2f7c-3530-4c17-965d-8a342bc7cd80@linux.intel.com> (raw)
In-Reply-To: <171951484029.775393.10885902747621916498.b4-ty@intel.com>
On 6/27/2024 9:00 PM, Lucas De Marchi wrote:
> On Tue, 25 Jun 2024 11:42:28 +0200, Nirmoy Das wrote:
>> xe_force_wake_get() can return error so check it's return value
>> before reading gpu_timestamp value.
>>
>> v2: set HWE to NULL instead of setting timestamp to 0(Lucas)
>> Add a warn on for xe_force_wake_put(Himal)
>>
>>
>> [...]
> Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
>
> and applied to drm-xe-next, thanks!
>
> [1/1] drm/xe/client: Check return value of xe_force_wake_get
> commit: e71cf19e3119de446cc37ddabb2e161ebbf7357c
Thanks Lucas!
>
> Best regards,
prev parent reply other threads:[~2024-06-28 8:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 9:42 [PATCH RESEND] drm/xe/client: Check return value of xe_force_wake_get Nirmoy Das
2024-06-25 10:00 ` Nirmoy Das
2024-06-25 10:02 ` ✓ CI.Patch_applied: success for drm/xe/client: Check return value of xe_force_wake_get (rev5) Patchwork
2024-06-25 10:02 ` ✓ CI.checkpatch: " Patchwork
2024-06-25 10:03 ` ✓ CI.KUnit: " Patchwork
2024-06-25 10:15 ` ✓ CI.Build: " Patchwork
2024-06-25 10:17 ` ✗ CI.Hooks: failure " Patchwork
2024-06-25 10:19 ` ✓ CI.checksparse: success " Patchwork
2024-06-25 10:42 ` ✓ CI.BAT: " Patchwork
2024-06-25 13:17 ` ✗ CI.FULL: failure " Patchwork
2024-06-27 19:00 ` [PATCH RESEND] drm/xe/client: Check return value of xe_force_wake_get Lucas De Marchi
2024-06-28 8:48 ` Nirmoy Das [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=2fca2f7c-3530-4c17-965d-8a342bc7cd80@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=nirmoy.das@intel.com \
--cc=rodrigo.vivi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.