From: Jerome Forissier <jerome@forissier.org>
To: Maxim Uvarov <maxim.uvarov@linaro.org>,
linux-kernel@vger.kernel.org, tee-dev@lists.linaro.org
Cc: gregkh@linuxfoundation.org, jarkko.sakkinen@linux.intel.com,
jgg@ziepe.ca, arnd@linaro.org, linux-integrity@vger.kernel.org,
peterhuewe@gmx.de
Subject: Re: [Tee-dev] [PATCHv3 2/3] optee: use uuid for sysfs driver entry
Date: Mon, 25 May 2020 14:10:25 +0200 [thread overview]
Message-ID: <7de3fea9-cd88-4dbf-aa27-3cb188fd6e85@forissier.org> (raw)
In-Reply-To: <20200525115235.5405-3-maxim.uvarov@linaro.org>
On 5/25/20 1:52 PM, Maxim Uvarov wrote:
> Optee device names for sysfs needed to be unique
s/Optee/OP-TEE/
s/needed/need/
> and it's better if they will mean something. UUID for name
> looks like good solution:
> /sys/bus/tee/devices/optee-clnt-<uuid>
How about mentioning it is the UUID of the Trusted Application on the
TEE side?
>
> Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>
> ---
> drivers/tee/optee/device.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Thanks,
--
Jerome
next prev parent reply other threads:[~2020-05-25 12:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 11:52 [PATCHv3 0/3] optee: register drivers on optee bus Maxim Uvarov
2020-05-25 11:52 ` [PATCHv3 1/3] optee: do drivers initialization before and after tee-supplicant run Maxim Uvarov
2020-05-27 19:55 ` Jarkko Sakkinen
2020-05-28 8:26 ` Maxim Uvarov
2020-05-25 11:52 ` [PATCHv3 2/3] optee: use uuid for sysfs driver entry Maxim Uvarov
2020-05-25 12:10 ` Jerome Forissier [this message]
2020-05-25 13:36 ` [Tee-dev] " Maxim Uvarov
2020-05-25 15:53 ` Jerome Forissier
2020-05-26 10:37 ` Sumit Garg
2020-05-25 12:47 ` Greg KH
2020-05-25 13:33 ` Maxim Uvarov
2020-05-25 11:52 ` [PATCHv3 3/3] tpm_ftpm_tee: register driver on TEE bus Maxim Uvarov
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=7de3fea9-cd88-4dbf-aa27-3cb188fd6e85@forissier.org \
--to=jerome@forissier.org \
--cc=arnd@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxim.uvarov@linaro.org \
--cc=peterhuewe@gmx.de \
--cc=tee-dev@lists.linaro.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®