dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karol Wachowski <karol.wachowski@linux.intel.com>
To: Jeff Hugo <jeff.hugo@oss.qualcomm.com>, dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, maciej.falkowski@linux.intel.com,
	lizhi.hou@amd.com,
	Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>
Subject: Re: [PATCH v2] accel/ivpu: Return correct job error status
Date: Wed, 8 Oct 2025 18:40:13 +0200	[thread overview]
Message-ID: <ddbec02e-29c8-452b-a95a-59fbd7eb3d10@linux.intel.com> (raw)
In-Reply-To: <b84df96a-16c9-4369-b3a2-7f4204416261@oss.qualcomm.com>


On 10/8/2025 5:03 PM, Jeff Hugo wrote:
> On 10/8/2025 12:12 AM, Karol Wachowski wrote:
>> From: Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>
>>
>> The driver was returning ABORTED for all errors that trigger engine
>> reset.
>
> This is past tense (was). I believe coding style says that commit text
> should be in the present tense (is). "The driver is returning ABORTED..." 
Fixed that commit message before merging.
>
>> It is better to distinguish between different error types by returning
>> the actual error code reported by firmware. This allows userspace to
>> take different actions based on the error type and improves
>> debuggability.
>>
>> Refactor ivpu_job_signal_and_destroy() by extracting engine error
>> handling logic into a new function ivpu_job_handle_engine_error().
>> This simplifies engine error handling logic by removing necessity of
>> calling ivpu_job_singal_and_destroy() multiple times by a single job
>> changing it's behavior based on job status.
>>
>> Signed-off-by: Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>
>> Signed-off-by: Karol Wachowski <karol.wachowski@linux.intel.com>
>
> I don't see a need for a v3 to do a minor tweak to the commit text
> when it seems reasonable to just inline that at merge. 
Thank you. Applied with corrected text to drm-misc-next.
>
> Reviewed-by: Jeff Hugo <jeff.hugo@oss.qualcomm.com>

      reply	other threads:[~2025-10-08 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-08  6:12 [PATCH v2] accel/ivpu: Return correct job error status Karol Wachowski
2025-10-08 15:03 ` Jeff Hugo
2025-10-08 16:40   ` Karol Wachowski [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=ddbec02e-29c8-452b-a95a-59fbd7eb3d10@linux.intel.com \
    --to=karol.wachowski@linux.intel.com \
    --cc=andrzej.kacprowski@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jeff.hugo@oss.qualcomm.com \
    --cc=lizhi.hou@amd.com \
    --cc=maciej.falkowski@linux.intel.com \
    --cc=oded.gabbay@gmail.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