All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Maxim Uvarov <maxim.uvarov@linaro.org>
Cc: linux-kernel@vger.kernel.org, tee-dev@lists.linaro.org,
	peterhuewe@gmx.de, jarkko.sakkinen@linux.intel.com, jgg@ziepe.ca,
	jens.wiklander@linaro.org, linux-integrity@vger.kernel.org,
	arnd@linaro.org, sumit.garg@linaro.org
Subject: Re: [PATCHv3 2/3] optee: use uuid for sysfs driver entry
Date: Mon, 25 May 2020 14:47:53 +0200	[thread overview]
Message-ID: <20200525124753.GA797117@kroah.com> (raw)
In-Reply-To: <20200525115235.5405-3-maxim.uvarov@linaro.org>

On Mon, May 25, 2020 at 02:52:34PM +0300, Maxim Uvarov wrote:
> Optee device names for sysfs needed to be unique
> and it's better if they will mean something. UUID for name
> looks like good solution:
> /sys/bus/tee/devices/optee-clnt-<uuid>

Can you document that in Documentation/ABI/ ?

And why UUID?  Those are usually huge, is that easier than just a unique
number?

thanks,

greg k-h

  parent reply	other threads:[~2020-05-25 12:47 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   ` [Tee-dev] " Jerome Forissier
2020-05-25 13:36     ` Maxim Uvarov
2020-05-25 15:53       ` Jerome Forissier
2020-05-26 10:37         ` Sumit Garg
2020-05-25 12:47   ` Greg KH [this message]
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=20200525124753.GA797117@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@linaro.org \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jens.wiklander@linaro.org \
    --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=sumit.garg@linaro.org \
    --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 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.