[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251204145716.GDaTGhTEHNOtSdTkEe@fat_crate.local>
Date: Thu, 4 Dec 2025 15:57:16 +0100
From: Borislav Petkov <bp@...en8.de>
To: Tom Lendacky <thomas.lendacky@....com>
Cc: Borislav Petkov <bp@...nel.org>, linux-coco@...ts.linux.dev,
X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3] x86/sev: Move the internal header
On Thu, Dec 04, 2025 at 08:18:42AM -0600, Tom Lendacky wrote:
> > +#include "../coco/sev/internal.h"
>
> Shouldn't this be "../../coco/sev/internal.h" ?
>
> What is strange is that it works with either.
Pure luck :-\
gcc cmdline is:
gcc -Wp,-MMD,arch/x86/boot/startup/.sev-startup.o.d -nostdinc
-I./arch/x86/include...
so the include path becomes:
# 1 "./arch/x86/include/../coco/sev/internal.h" 1
which is
$ readlink -f arch/x86/include/../coco/sev/internal.h
/mnt/kernel/kernel/linux/arch/x86/coco/sev/internal.h
And /mnt/kernel is my kernel-sources-containing SSD :-)
In any case, good catch!
I'll do the "../../" so that it is perfectly clear and future
potential include directives changes do not break this.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists