From: Florian Fainelli <f.fainelli@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Allen Pais" <apais@linux.microsoft.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafał Miłecki" <zajec5@gmail.com>,
"Christoph Hellwig" <hch@lst.de>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH v3 1/1] firmware: tee_bnxt: Use UUID API for exporting the UUID
Date: Tue, 3 May 2022 12:28:18 -0700 [thread overview]
Message-ID: <092fbb39-9a62-80ce-b3bc-62a597d8a718@gmail.com> (raw)
In-Reply-To: <YnEBtk4ltlsep5/m@smile.fi.intel.com>
On 5/3/22 03:19, Andy Shevchenko wrote:
> On Wed, Apr 13, 2022 at 08:38:41AM -0700, Florian Fainelli wrote:
>> On 4/12/2022 4:32 AM, 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.
>>>
>>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>>> ---
>>> v3: rebased on the latest vanilla, added Andrew since it has no move for 1y+
>>
>> I don't think this is going to be picked up unless we designate a entry in
>> the MAINTAINERS file, I don't mind taking this via the Broadcom ARM SoCs
>> pull request if this does not move.
>
> I saw your patch has been picked up to up-to-date MAINTAINERS record.
> Can this one now be picked up too?
Please resubmit targeting David Miller's net-next tree since this is how
patches would be merged moving forward. Thanks!
--
Florian
next prev parent reply other threads:[~2022-05-03 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 11:32 [PATCH v3 1/1] firmware: tee_bnxt: Use UUID API for exporting the UUID Andy Shevchenko
2022-04-13 15:38 ` Florian Fainelli
2022-04-13 16:51 ` Andy Shevchenko
2022-05-03 10:19 ` Andy Shevchenko
2022-05-03 19:28 ` Florian Fainelli [this message]
2022-05-04 9:14 ` Andy Shevchenko
2022-04-13 16:43 ` Christoph Hellwig
2022-04-13 16:52 ` 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=092fbb39-9a62-80ce-b3bc-62a597d8a718@gmail.com \
--to=f.fainelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=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