From: Florian Fainelli <f.fainelli@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Allen Pais" <apais@linux.microsoft.com>,
netdev@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org, "Rafał Miłecki" <zajec5@gmail.com>,
"Michael Chan" <michael.chan@broadcom.com>,
"Christoph Hellwig" <hch@lst.de>
Subject: Re: [PATCH v4 1/1] firmware: tee_bnxt: Use UUID API for exporting the UUID
Date: Thu, 5 May 2022 10:17:47 -0700 [thread overview]
Message-ID: <9eb82218-95ed-de7f-8a80-31b266d43380@gmail.com> (raw)
In-Reply-To: <20220505093938.571702fd@kernel.org>
On 5/5/22 09:39, Jakub Kicinski wrote:
> On Wed, 4 May 2022 12:14:07 +0300 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>
>> Reviewed-by: Christoph Hellwig <hch@lst.de>
>> ---
>> v4: added tag (Christoph), resent with 126858db81a5 (in next) in mind (Florian)
>
> Judging by the history of the file this may go via the tee tree or
> net-next. Since tee was not CCed I presume the latter is preferred.
> Please let us know if that's incorrect otherwise we'll apply tomorrow :)
This file has historically been without a maintainer or tree, but since
it is somewhat related to the bnxt driver, I eventually signed up
Michael to also review such patches:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=126858db81a5094d20885bc59621c3b9497f9048
If you could apply it via netdev-next/master that owuld be great, thanks!
--
Florian
next prev parent reply other threads:[~2022-05-05 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 9:14 [PATCH v4 1/1] firmware: tee_bnxt: Use UUID API for exporting the UUID Andy Shevchenko
2022-05-05 16:39 ` Jakub Kicinski
2022-05-05 17:17 ` Florian Fainelli [this message]
2022-05-06 2:00 ` patchwork-bot+netdevbpf
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=9eb82218-95ed-de7f-8a80-31b266d43380@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=apais@linux.microsoft.com \
--cc=hch@lst.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@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).