From: Greg KH <greg@kroah.com>
To: Nicolas Schier <n.schier@avm.de>
Cc: stable@vger.kernel.org, Jing Leng <jleng@ambarella.com>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH 5.4] kbuild: Fix include path in scripts/Makefile.modpost
Date: Thu, 1 Sep 2022 12:20:57 +0200 [thread overview]
Message-ID: <YxCHiTdsFI4WRF7F@kroah.com> (raw)
In-Reply-To: <20220831041724.1493230-1-n.schier@avm.de>
On Wed, Aug 31, 2022 at 06:17:24AM +0200, Nicolas Schier wrote:
> From: Jing Leng <jleng@ambarella.com>
>
> commit 23a0cb8e3225122496bfa79172005c587c2d64bf upstream.
>
> When building an external module, if users don't need to separate the
> compilation output and source code, they run the following command:
> "make -C $(LINUX_SRC_DIR) M=$(PWD)". At this point, "$(KBUILD_EXTMOD)"
> and "$(src)" are the same.
>
> If they need to separate them, they run "make -C $(KERNEL_SRC_DIR)
> O=$(KERNEL_OUT_DIR) M=$(OUT_DIR) src=$(PWD)". Before running the
> command, they need to copy "Kbuild" or "Makefile" to "$(OUT_DIR)" to
> prevent compilation failure.
>
> So the kernel should change the included path to avoid the copy operation.
>
> Signed-off-by: Jing Leng <jleng@ambarella.com>
> [masahiro: I do not think "M=$(OUT_DIR) src=$(PWD)" is the official way,
> but this patch is a nice clean up anyway.]
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> [nsc: updated context for v5.4]
> Signed-off-by: Nicolas Schier <n.schier@avm.de>
> ---
> scripts/Makefile.modpost | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/scripts/Makefile.modpost b/scripts/Makefile.modpost
> index 48585c4d04ad..0273bf7375e2 100644
> --- a/scripts/Makefile.modpost
> +++ b/scripts/Makefile.modpost
> @@ -87,8 +87,7 @@ obj := $(KBUILD_EXTMOD)
> src := $(obj)
>
> # Include the module's Makefile to find KBUILD_EXTRA_SYMBOLS
> -include $(if $(wildcard $(KBUILD_EXTMOD)/Kbuild), \
> - $(KBUILD_EXTMOD)/Kbuild, $(KBUILD_EXTMOD)/Makefile)
> +include $(if $(wildcard $(src)/Kbuild), $(src)/Kbuild, $(src)/Makefile)
>
> # modpost option for external modules
> MODPOST += -e
> --
> 2.37.2
>
Does not apply to the 5.4.y tree at all, are you sure you generated this
properly?
thanks,
greg k-h
next prev parent reply other threads:[~2022-09-01 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 4:17 [PATCH 5.4] kbuild: Fix include path in scripts/Makefile.modpost Nicolas Schier
2022-09-01 10:20 ` Greg KH [this message]
2022-09-01 10:29 ` Nicolas Schier
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=YxCHiTdsFI4WRF7F@kroah.com \
--to=greg@kroah.com \
--cc=jleng@ambarella.com \
--cc=masahiroy@kernel.org \
--cc=n.schier@avm.de \
--cc=stable@vger.kernel.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