On Mon, Apr 28, 2025 at 4:30 PM Mario Limonciello superm1@kernel.org wrote:
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.
I wasn't aware of kworkflow. I'm usually building manually locally or with tuxbuild.
Can you share your .config? Is it a defconfig?
It's defconfig + CONFIG_CRYPTO_DEV_CCP=y to get AMDTEE enabled. If you have an easier way, please let me know.
Let me pull the tee tree directly and try again with that tree and I'll see if I can reproduce the build error.
The error is: security/selinux/nlmsgtab.c: In function ‘selinux_nlmsg_lookup’: security/selinux/nlmsgtab.c:188:33: error: ‘NETLINK_ROUTE_SOCKET__NLMSG’ undeclared (first use in this function); did you mean ‘NETLINK_ROUTE_SOCKET__LOCK’? 188 | *perm = NETLINK_ROUTE_SOCKET__NLMSG;
Cheers, Jens