From: Randy Dunlap <rdunlap@infradead.org>
To: "Enrico Weigelt, metux IT consult" <info@metux.net>,
linux-kernel@vger.kernel.org
Cc: michal.lkml@markovi.net, linux-kbuild@vger.kernel.org,
yamada.masahiro@socionext.com,
clang-built-linux@googlegroups.com, apw@canonical.com,
joe@perches.com, linux-riscv@lists.infradead.org
Subject: Re: [PATCH 1/4] Makefile: rules for printing kernel architecture and localversion
Date: Tue, 9 Jul 2019 07:54:06 -0700 [thread overview]
Message-ID: <3d4da301-618e-e348-2a6a-144b802d240f@infradead.org> (raw)
In-Reply-To: <1562664759-16009-1-git-send-email-info@metux.net>
On 7/9/19 2:32 AM, Enrico Weigelt, metux IT consult wrote:
> 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>
Hi,
If accepted, these targets should be added to the top level Makefile's
"make help" output also.
Thanks.
> ---
> Makefile | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Makefile b/Makefile
> index 3e4868a..5afc3de 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1706,6 +1706,12 @@ kernelrelease:
> kernelversion:
> @echo $(KERNELVERSION)
>
> +kernellocalversion:
> + @$(CONFIG_SHELL) $(srctree)/scripts/setlocalversion $(srctree) | sed -e 's~^\-~~'
> +
> +kernelarch:
> + @echo $(ARCH)
> +
> image_name:
> @echo $(KBUILD_IMAGE)
>
>
--
~Randy
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2019-07-09 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 9:32 [PATCH 1/4] Makefile: rules for printing kernel architecture and localversion Enrico Weigelt, metux IT consult
2019-07-09 9:32 ` [PATCH 2/4] scripts: mkdebian: allow renaming generated debian/rules via env Enrico Weigelt, metux IT consult
2019-07-09 9:32 ` [PATCH 3/4] scripts: checkpatch.pl: don't complain that debian/rules is executable Enrico Weigelt, metux IT consult
2019-07-09 10:16 ` Joe Perches
2019-07-09 9:32 ` [PATCH 4/4] debian: add generic rule file Enrico Weigelt, metux IT consult
2019-07-15 12:28 ` Masahiro Yamada
2019-07-15 18:56 ` Enrico Weigelt, metux IT consult
2019-07-15 19:12 ` Theodore Y. Ts'o
2019-07-16 8:58 ` Masahiro Yamada
2019-07-16 12:34 ` Theodore Y. Ts'o
2019-07-17 14:16 ` Enrico Weigelt, metux IT consult
2019-07-17 15:23 ` Theodore Y. Ts'o
2019-07-17 11:08 ` Enrico Weigelt, metux IT consult
2019-07-09 14:54 ` Randy Dunlap [this message]
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=3d4da301-618e-e348-2a6a-144b802d240f@infradead.org \
--to=rdunlap@infradead.org \
--cc=apw@canonical.com \
--cc=clang-built-linux@googlegroups.com \
--cc=info@metux.net \
--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;
as well as URLs for NNTP newsgroup(s).