From: Mario Limonciello <superm1@kernel.org>
To: op-tee@lists.trustedfirmware.org
Subject: Re: [PATCH 0/2] small amdtee cleanups
Date: Mon, 28 Apr 2025 09:30:50 -0500 [thread overview]
Message-ID: <86167ea5-8bc4-4aa6-a980-8d9e37c776ae@kernel.org> (raw)
In-Reply-To: < <CAHUa44EczHYv0mNrMMbF-Vwc3jbOJqPy5sMsiW=0v2o1UaVfBw@mail.gmail.com>>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
On 4/28/2025 9:27 AM, Jens Wiklander wrote:
> Hi,
>
> On Mon, Apr 21, 2025 at 5:22 PM Mario Limonciello <superm1@kernel.org> wrote:
>>
>> From: Mario Limonciello <mario.limonciello@amd.com>
>>
>> I just noticed a few small things for amdtee where the error messages
>> didn't consistently use the driver name. While fixing that I noticed
>> the headers weren't sorted.
>>
>> These patches fix both issues.
>>
>> Mario Limonciello (2):
>> tee: Use pr_fmt for messages
>> tee: Sort header includes
>>
>> drivers/tee/amdtee/core.c | 16 +++++++++-------
>> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> I'm trying to build this, but I run into some selinux build error. How
> did you build this?
I used kworkflow (kw b). It was based off linux-next at the time I
submitted it.
Can you share your .config? Is it a defconfig?
Let me pull the tee tree directly and try again with that tree and I'll
see if I can reproduce the build error.
next parent reply other threads:[~2025-04-28 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] < <CAHUa44EczHYv0mNrMMbF-Vwc3jbOJqPy5sMsiW=0v2o1UaVfBw@mail.gmail.com>
2025-04-28 14:30 ` Mario Limonciello [this message]
2025-04-28 14:41 ` [PATCH 0/2] small amdtee cleanups Jens Wiklander
[not found] < <CAHUa44GrjAAz9HxN2Uy-KOTuLe21w-EsT8mTcaqoh4JUErtXbQ@mail.gmail.com>
2025-04-29 13:08 ` Mario Limonciello
[not found] < <CAHUa44GCZN197c=FHAmuUkZk0EQLxZ-sbwjvu-08NDjgRA1j2Q@mail.gmail.com>
2025-04-28 17:47 ` Mario Limonciello
2025-04-29 9:08 ` Jens Wiklander
2025-04-21 15:22 Mario Limonciello
2025-04-28 14:27 ` Jens Wiklander
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=86167ea5-8bc4-4aa6-a980-8d9e37c776ae@kernel.org \
--to=superm1@kernel.org \
--cc=op-tee@lists.trustedfirmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox