[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <803eabc8e2fa5dec950d149f83027fd204d5ef69.camel@intel.com>
Date: Fri, 28 Jun 2024 21:23:54 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "masahiroy@...nel.org" <masahiroy@...nel.org>
CC: "nicolas@...sle.eu" <nicolas@...sle.eu>, "conor@...nel.org"
<conor@...nel.org>, "devicetree@...r.kernel.org"
<devicetree@...r.kernel.org>, "robh@...nel.org" <robh@...nel.org>,
"linux-kbuild@...r.kernel.org" <linux-kbuild@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"krzk@...nel.org" <krzk@...nel.org>
Subject: Re: [PATCH v2 4/4] kbuild: use $(src) instead of $(srctree)/$(src)
for source directory
On Fri, 2024-06-28 at 11:13 +0900, Masahiro Yamada wrote:
> There are two solutions, depending on what you want to achieve.
>
> The official way is to pass the absolute path to M=
> (or relative path to ../linux-tdm-kvm-out)
>
> The other unofficial way is to pass VPATH.
> The external module build does not officially support
> the separate output directory, but you can still
> do it in this case.
>
> [1] will work like before.
The absolute path worked, but why not make it use the relative path by default
in this case? "arch/x86/kvm/" shouldn't be confused with an absolute path...
Powered by blists - more mailing lists