From: Matthew Auld <matthew.auld@intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>, intel-xe@lists.freedesktop.org
Cc: stable@vger.kernel.org,
Bommu Krishnaiah <krishnaiah.bommu@intel.com>,
Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH v2] drm/xe/ufence: ufence can be signaled right after wait_woken
Date: Mon, 14 Oct 2024 08:53:33 +0100 [thread overview]
Message-ID: <a8e10e81-8f54-44da-b8af-a10dd7f55f6a@intel.com> (raw)
In-Reply-To: <20241011151029.4160630-1-nirmoy.das@intel.com>
On 11/10/2024 16:10, Nirmoy Das wrote:
> do_comapre() can return success after a timedout wait_woken() which was
s/comapre/compare
> treated as -ETIME. The loop calling wait_woken() sets correct err so
> there is no need to re-evaluate err.
>
> v2: Remove entire check that reevaluate err at the end(Matt)
>
> Fixes: e670f0b4ef24 ("drm/xe/uapi: Return correct error code for xe_wait_user_fence_ioctl")
> Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/1630
> Cc: <stable@vger.kernel.org> # v6.8+
> Cc: Bommu Krishnaiah <krishnaiah.bommu@intel.com>
> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
prev parent reply other threads:[~2024-10-14 7:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 15:10 [PATCH v2] drm/xe/ufence: ufence can be signaled right after wait_woken Nirmoy Das
2024-10-11 19:54 ` ✓ CI.Patch_applied: success for drm/xe/ufence: ufence can be signaled right after wait_woken (rev2) Patchwork
2024-10-11 19:54 ` ✓ CI.checkpatch: " Patchwork
2024-10-11 19:56 ` ✓ CI.KUnit: " Patchwork
2024-10-11 20:11 ` ✓ CI.Build: " Patchwork
2024-10-11 20:13 ` ✓ CI.Hooks: " Patchwork
2024-10-11 20:15 ` ✓ CI.checksparse: " Patchwork
2024-10-12 2:07 ` [PATCH v2] drm/xe/ufence: ufence can be signaled right after wait_woken Matthew Brost
2024-10-12 2:35 ` ✗ CI.FULL: failure for drm/xe/ufence: ufence can be signaled right after wait_woken (rev2) Patchwork
2024-10-14 8:06 ` Nirmoy Das
2024-10-14 7:53 ` Matthew Auld [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=a8e10e81-8f54-44da-b8af-a10dd7f55f6a@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=krishnaiah.bommu@intel.com \
--cc=matthew.brost@intel.com \
--cc=nirmoy.das@intel.com \
--cc=stable@vger.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