From: Mario Limonciello <mario.limonciello@amd.com>
To: Lizhi Hou <lizhi.hou@amd.com>,
ogabbay@kernel.org, quic_jhugo@quicinc.com,
dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, min.ma@amd.com, max.zhen@amd.com,
sonal.santan@amd.com, king.tam@amd.com
Subject: Re: [PATCH V3 5/5] accel/amdxdna: Add zero check for pad in ioctl input structures
Date: Mon, 16 Dec 2024 16:00:39 -0600 [thread overview]
Message-ID: <1d3c8249-2b2f-465e-810b-848968de9abd@amd.com> (raw)
In-Reply-To: <cf132e81-524b-3b13-aa18-4f542f7ca480@amd.com>
>> This change actually meant here? It seems like it should be it's own
>> change.
>
> Agree. Hopefully, the patch 1 - 4 are good to go and I do not need to
> resend them. :)
>
>
Yeah those are fine at this point. They've gotten good feedback, no
complaints from LKP robot. I think you can just send the fixed up patch
5 separately.
I've just added 1-4 to drm-misc-next. Here are the hashes.
b1dcfe620574b accel/amdxdna: Read firmware interface version from registers
f4d7b8a6bc8c9 accel/amdxdna: Enhance power management settings
a37d78470bcc8 accel/amdxdna: Replace idr api with xarray
273b5176ac178 accel/amdxdna: Add RyzenAI-npu6 support
prev parent reply other threads:[~2024-12-16 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 23:29 [PATCH V3 0/5] AMD NPU driver improvements Lizhi Hou
2024-12-13 23:29 ` [PATCH V3 1/5] accel/amdxdna: Add RyzenAI-npu6 support Lizhi Hou
2024-12-13 23:29 ` [PATCH V3 2/5] accel/amdxdna: Replace idr api with xarray Lizhi Hou
2024-12-16 21:54 ` Mario Limonciello
2024-12-13 23:29 ` [PATCH V3 3/5] accel/amdxdna: Enhance power management settings Lizhi Hou
2024-12-13 23:29 ` [PATCH V3 4/5] accel/amdxdna: Read firmware interface version from registers Lizhi Hou
2024-12-13 23:29 ` [PATCH V3 5/5] accel/amdxdna: Add zero check for pad in ioctl input structures Lizhi Hou
2024-12-16 20:38 ` Mario Limonciello
2024-12-16 21:03 ` Lizhi Hou
2024-12-16 22:00 ` Mario Limonciello [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=1d3c8249-2b2f-465e-810b-848968de9abd@amd.com \
--to=mario.limonciello@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=king.tam@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=max.zhen@amd.com \
--cc=min.ma@amd.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--cc=sonal.santan@amd.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.