From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH ltp] m4/ltp-kernel_devel.m4: get LINUX_VERSION from LINUX_DIR during configure
Date: Mon, 4 Jun 2018 13:24:02 +0200 [thread overview]
Message-ID: <20180604112402.GA3362@rei> (raw)
In-Reply-To: <20180604063306.24325-1-yixin.zhang@intel.com>
Hi!
> If LINUX_DIR is given, get LINUX_VERSION for kernel source code instead
> of `uname -r`. So when we need to build .ko with a kernel differernt
> than the one on current host PC, we only need to provide
> "--with-linux-dir", and LINUX_VERSION will be generated automatically.
Looking at the m4 file for kernel-devel it seems we only use the
LINUX_VERSION in order to construct the LINUX_DIR path and the rest of
the code, i.e. include/mk/module.mk uses the LINUX_VERSION_MAJOR and
LINUX_VERSION_MINOR generated based on the LINUX_DIR.
What is the LINUX_VERSION variable needed for? It does not seem to be
used anywhere outside the m4 kernel devel file.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2018-06-04 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 6:33 [LTP] [PATCH ltp] m4/ltp-kernel_devel.m4: get LINUX_VERSION from LINUX_DIR during configure Yixin Zhang
2018-06-04 11:24 ` Cyril Hrubis [this message]
2018-06-05 1:24 ` Zhang, Yixin
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=20180604112402.GA3362@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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