From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: yamada.masahiro@socionext.com, michal.lkml@markovi.net,
info@metux.net, apw@canonical.com, joe@perches.com,
linux-kbuild@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: [PATCH v1 1/5] Makefile: rules for printing kernel architecture and localversion
Date: Fri, 8 Mar 2019 13:44:20 +0100 [thread overview]
Message-ID: <1552049064-32044-2-git-send-email-info@metux.net> (raw)
In-Reply-To: <1552049064-32044-1-git-send-email-info@metux.net>
trivial rule to print out the kernel arch and localversion, so
external tools, like distro packagers, can easily get it.
Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
---
Makefile | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Makefile b/Makefile
index f070e0d..95b50f8 100644
--- a/Makefile
+++ b/Makefile
@@ -1664,6 +1664,12 @@ kernelrelease:
kernelversion:
@echo $(KERNELVERSION)
+kernellocalversion:
+ @$(CONFIG_SHELL) $(srctree)/scripts/setlocalversion $(srctree) | sed -e 's~^\-~~'
+
+kernelarch:
+ @echo $(ARCH)
+
image_name:
@echo $(KBUILD_IMAGE)
--
1.9.1
next prev parent reply other threads:[~2019-03-08 12:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 12:44 Debian build polishing Enrico Weigelt, metux IT consult
2019-03-08 12:44 ` Enrico Weigelt, metux IT consult [this message]
2019-03-08 12:44 ` [PATCH v1 2/5] scripts: mkdebian: allow renaming generated debian/rules via env Enrico Weigelt, metux IT consult
2019-03-08 12:44 ` [PATCH v1 3/5] scripts: mkdebian: fix missing dependencies Enrico Weigelt, metux IT consult
2019-03-08 12:44 ` [PATCH v1 4/5] scripts: checkpatch.pl: don't complain that debian/rules is executable Enrico Weigelt, metux IT consult
2019-03-08 14:13 ` Joe Perches
2019-03-08 12:44 ` [PATCH v1 5/5] debian: add generic rule file Enrico Weigelt, metux IT consult
2019-03-08 17:57 ` Debian build polishing Theodore Ts'o
2019-03-08 21:10 ` Enrico Weigelt, metux IT consult
2019-03-08 21:57 ` Theodore Ts'o
2019-03-10 18:50 ` Enrico Weigelt, metux IT consult
2019-03-11 16:19 ` 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=1552049064-32044-2-git-send-email-info@metux.net \
--to=info@metux.net \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michal.lkml@markovi.net \
--cc=yamada.masahiro@socionext.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