From: Sumit Garg <sumit.garg@kernel.org>
To: Andrew Davis <afd@ti.com>, Jens Wiklander <jenswi@kernel.org>,
Sumit Garg <sumit.garg@kernel.org>,
op-tee@lists.trustedfirmware.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tee: move tee_ioctl_shm_register_data to above IOCTL definition
Date: Thu, 10 Sep 2026 14:51:21 +0530 [thread overview]
Message-ID: <aqJ2kXdcapQI-RCQ@sumit-xelite> (raw)
In-Reply-To: <aqJ0yCHd03ZLsSMT@sumit-xelite>
On Thu, 10 Sep 2026 at 14:43:44 +0530, Sumit Garg via OP-TEE wrote:
>On Thu, 03 Sep 2026 at 12:57:30 -0500, Andrew Davis via OP-TEE wrote:
>>Most of the struct definitions for a given IOCTL definition immediately
>>preceded that definition. The struct tee_ioctl_shm_register_data is an
>>exception as it is placed above the TEE_IOC_SHM_REGISTER_FD definition,
>>not the TEE_IOC_SHM_REGISTER one it is to be used with. Move it down
>>to match the others.
>>
>>This is a non-functional change for consistency and to help prevent
>>someone from accidentally using the wrong struct with the wrong IOCTL
>>based on the struct's location.
>>
>>Fix a couple small spelling issues while here.
>>
>>Signed-off-by: Andrew Davis <afd@ti.com>
>>---
>>include/uapi/linux/tee.h | 40 ++++++++++++++++++++--------------------
>>1 file changed, 20 insertions(+), 20 deletions(-)
>>
>
>Reviewed-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
>
>-Sumit
Andrew,
Please check your get_maintainers script, it's too old to pick up wrong
maintainer's email ID. I have updated it now.
-Sumit
prev parent reply other threads:[~2026-09-10 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 17:57 Andrew Davis
2026-09-10 9:13 ` Sumit Garg
2026-09-10 9:21 ` Sumit Garg [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=aqJ2kXdcapQI-RCQ@sumit-xelite \
--to=sumit.garg@kernel.org \
--cc=afd@ti.com \
--cc=jenswi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.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
all inboxes | Powered by JetHome®