public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: nvidia@cohens.org.il
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	Masahiro Yamada <masahiroy@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Nicolas Schier <nicolas@fjasle.eu>,
	Tzafrir Cohen <nvidia@cohens.org.il>
Subject: [PATCH] Makefile: Make kernelrelease target work with M=
Date: Tue, 14 Mar 2023 15:02:48 +0200	[thread overview]
Message-ID: <20230314130248.954196-2-nvidia@cohens.org.il> (raw)
In-Reply-To: <20230314130248.954196-1-nvidia@cohens.org.il>

From: Tzafrir Cohen <nvidia@cohens.org.il>

Fixes: commit 1cb86b6c3136 ("kbuild: save overridden KERNELRELEASE in include/config/kernel.release")

That commit required the use of filechk_kernel.release for the
kernelrelease Makefile target. It is currently only being set when
KBUILD_EXTMOD is not set. Make sure it is set in that case as well.

Signed-off-by: Tzafrir Cohen <nvidia@cohens.org.il>
---
 Makefile | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Makefile b/Makefile
index 3e7f96f12f08..e0859c608147 100644
--- a/Makefile
+++ b/Makefile
@@ -1880,6 +1880,8 @@ endif
 
 else # KBUILD_EXTMOD
 
+filechk_kernel.release = echo $(KERNELRELEASE)
+
 ###
 # External module support.
 # When building external modules the kernel used as basis is considered
-- 
2.39.2


  reply	other threads:[~2023-03-14 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 13:02 Makefile: fix usage of kernelrelease with M=foo nvidia
2023-03-14 13:02 ` nvidia [this message]
2023-03-14 14:14   ` [PATCH] Makefile: Make kernelrelease target work with M= Masahiro Yamada

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=20230314130248.954196-2-nvidia@cohens.org.il \
    --to=nvidia@cohens.org.il \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    /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