All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
	linux-mips@vger.kernel.org,
	"Vikas Gupta" <vikas.gupta@broadcom.com>,
	"Jens Wiklander" <jens.wiklander@linaro.org>,
	tee-dev@lists.linaro.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [RESEND PATCH v1] firmware: tee_bnxt: Use UUID API for exporting the UUID
Date: Thu, 21 Jan 2021 20:37:41 +0200	[thread overview]
Message-ID: <20210121183741.45333-1-andriy.shevchenko@linux.intel.com> (raw)

There is export_uuid() function which exports uuid_t to the u8 array.
Use it instead of open coding variant.

This allows to hide the uuid_t internals.

Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
 drivers/firmware/broadcom/tee_bnxt_fw.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/firmware/broadcom/tee_bnxt_fw.c b/drivers/firmware/broadcom/tee_bnxt_fw.c
index ed10da5313e8..4cf0c2576037 100644
--- a/drivers/firmware/broadcom/tee_bnxt_fw.c
+++ b/drivers/firmware/broadcom/tee_bnxt_fw.c
@@ -197,7 +197,7 @@ static int tee_bnxt_fw_probe(struct device *dev)
 		return -ENODEV;
 
 	/* Open session with Bnxt load Trusted App */
-	memcpy(sess_arg.uuid, bnxt_device->id.uuid.b, TEE_IOCTL_UUID_LEN);
+	export_uuid(sess_arg.uuid, &bnxt_device->id.uuid);
 	sess_arg.clnt_login = TEE_IOCTL_LOGIN_PUBLIC;
 	sess_arg.num_params = 0;
 
-- 
2.29.2


             reply	other threads:[~2021-01-21 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 18:37 Andy Shevchenko [this message]
2021-12-13 20:36 ` [RESEND PATCH v1] firmware: tee_bnxt: Use UUID API for exporting the UUID Andy Shevchenko
2021-12-13 20:37   ` Andy Shevchenko
2022-01-04  9:24     ` Christoph Hellwig
2022-01-04 13:41       ` Andy Shevchenko
2022-01-27 16:02         ` Andy Shevchenko

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=20210121183741.45333-1-andriy.shevchenko@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=jens.wiklander@linaro.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=tee-dev@lists.linaro.org \
    --cc=vikas.gupta@broadcom.com \
    --cc=zajec5@gmail.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.