From: Johannes Berg <johannes@sipsolutions.net>
To: backports@vger.kernel.org
Cc: Johannes Berg <johannes.berg@intel.com>
Subject: [PATCH] backports: suppress errors from 'make kernelversion'
Date: Tue, 4 May 2021 22:59:20 +0200 [thread overview]
Message-ID: <20210504225919.393f7f931e90.I3aace2170f657561190f0473f2affafc850559b3@changeid> (raw)
From: Johannes Berg <johannes.berg@intel.com>
Since kernel 5.8, specifically commit 4d0831e8a029 ("kconfig: unify
cc-option and as-option"), 'make kernelversion' will call into the
Kconfig system, evaluating cc-option from scripts/Kconfig.include,
which requires a writable current working directory due to the use
of ".tmp_<pid>" for temporary files. This seems questionable, but
since the kernelversion really isn't affected, we can ignore it.
I also mentioned this upstream, see the thread after the commit:
https://lore.kernel.org/r/20200614144341.1077495-2-masahiroy@kernel.org
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
---
backport/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/backport/Makefile b/backport/Makefile
index ee7df4ba29ce..2bdea02d4a46 100644
--- a/backport/Makefile
+++ b/backport/Makefile
@@ -84,8 +84,8 @@ mrproper:
echo "" ;\
done \
) > Kconfig.kernel ;\
- kver=$$($(MAKE) --no-print-directory -C $(KLIB_BUILD) kernelversion | \
- sed 's/^\(\([3-5]\|2\.6\)\.[0-9]\+\).*/\1/;t;d') ;\
+ kver=$$($(MAKE) --no-print-directory -C $(KLIB_BUILD) kernelversion \
+ 2>/dev/null | sed 's/^\(\([3-5]\|2\.6\)\.[0-9]\+\).*/\1/;t;d') ;\
test "$$kver" != "" || echo "Kernel version parse failed!" ;\
test "$$kver" != "" ;\
kvers="$$(seq 14 39 | sed 's/^/2.6./')" ;\
--
2.30.2
--
To unsubscribe from this list: send the line "unsubscribe backports" in
reply other threads:[~2021-05-04 20:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210504225919.393f7f931e90.I3aace2170f657561190f0473f2affafc850559b3@changeid \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=johannes.berg@intel.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).