From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Allen Pais <apais@linux.microsoft.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Rafał Miłecki" <zajec5@gmail.com>, "Christoph Hellwig" <hch@lst.de>
Subject: Re: [PATCH v2 1/1] firmware: tee_bnxt: Use UUID API for exporting the UUID
Date: Thu, 3 Feb 2022 17:05:45 +0200 [thread overview]
Message-ID: <YfvvSTrSv3lv4CEE@smile.fi.intel.com> (raw)
In-Reply-To: <20220127160150.48140-1-andriy.shevchenko@linux.intel.com>
On Thu, Jan 27, 2022 at 06:01:50PM +0200, Andy Shevchenko wrote:
> 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.
Any comments, tags? Can it be accepted now?
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-02-03 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 16:01 [PATCH v2 1/1] firmware: tee_bnxt: Use UUID API for exporting the UUID Andy Shevchenko
2022-02-03 15:05 ` Andy Shevchenko [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=YfvvSTrSv3lv4CEE@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=apais@linux.microsoft.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).