From: Lizhi Hou <lizhi.hou@amd.com>
To: Qianfeng Rong <rongqianfeng@vivo.com>, Min Ma <min.ma@amd.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] accel/amdxdna: Use int instead of u32 to store error codes
Date: Fri, 29 Aug 2025 09:02:54 -0700 [thread overview]
Message-ID: <3d2e37d4-3ef0-4062-a693-0b73ed82a497@amd.com> (raw)
In-Reply-To: <9c722376-da4f-c09e-3aac-1a06091791c0@amd.com>
Applied to drm-misc-next.
On 8/28/25 13:23, Lizhi Hou wrote:
> Reviewed-by: Lizhi Hou <lizhi.hou@amd.com>
>
> On 8/27/25 20:39, Qianfeng Rong wrote:
>> Change the 'ret' variable from u32 to int to store -EINVAL. Storing the
>> negative error codes in unsigned type, doesn't cause an issue at runtime
>> but it's ugly as pants.
>>
>> Additionally, assigning -EINVAL to u32 ret (i.e., u32 ret = -EINVAL) may
>> trigger a GCC warning when the -Wsign-conversion flag is enabled.
>>
>> Fixes: aac243092b70 ("accel/amdxdna: Add command execution")
>> Signed-off-by: Qianfeng Rong <rongqianfeng@vivo.com>
>> ---
>> v2: Modified commit message and add a fixes tag as suggested by Lizhi.
>> ---
>> drivers/accel/amdxdna/aie2_ctx.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/accel/amdxdna/aie2_ctx.c
>> b/drivers/accel/amdxdna/aie2_ctx.c
>> index 420467a5325c..e9f9b1fa5dc1 100644
>> --- a/drivers/accel/amdxdna/aie2_ctx.c
>> +++ b/drivers/accel/amdxdna/aie2_ctx.c
>> @@ -199,7 +199,7 @@ aie2_sched_resp_handler(void *handle, void
>> __iomem *data, size_t size)
>> {
>> struct amdxdna_sched_job *job = handle;
>> struct amdxdna_gem_obj *cmd_abo;
>> - u32 ret = 0;
>> + int ret = 0;
>> u32 status;
>> cmd_abo = job->cmd_bo;
>> @@ -229,7 +229,7 @@ static int
>> aie2_sched_nocmd_resp_handler(void *handle, void __iomem *data,
>> size_t size)
>> {
>> struct amdxdna_sched_job *job = handle;
>> - u32 ret = 0;
>> + int ret = 0;
>> u32 status;
>> if (unlikely(!data))
>> @@ -257,7 +257,7 @@ aie2_sched_cmdlist_resp_handler(void *handle,
>> void __iomem *data, size_t size)
>> u32 fail_cmd_status;
>> u32 fail_cmd_idx;
>> u32 cmd_status;
>> - u32 ret = 0;
>> + int ret = 0;
>> cmd_abo = job->cmd_bo;
>> if (unlikely(!data) || unlikely(size != sizeof(u32) * 3)) {
prev parent reply other threads:[~2025-08-29 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 3:39 Qianfeng Rong
2025-08-28 20:23 ` Lizhi Hou
2025-08-29 16:02 ` Lizhi Hou [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=3d2e37d4-3ef0-4062-a693-0b73ed82a497@amd.com \
--to=lizhi.hou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=min.ma@amd.com \
--cc=ogabbay@kernel.org \
--cc=rongqianfeng@vivo.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
all inboxes | Powered by JetHome®