From: Umang Jain <umang.jain@ideasonboard.com>
To: smatch@vger.kernel.org
Subject: Kernel config usage
Date: Thu, 2 Nov 2023 14:30:18 +0530 [thread overview]
Message-ID: <bfc8a5ff-7571-fbcd-2b1f-54af2571d133@ideasonboard.com> (raw)
Hello,
I am reading
https://repo.or.cz/smatch.git/blob/HEAD:/Documentation/smatch.txt
And trying to test smatch against the linux kernel staging branch from
Greg KH's repo.
I am a bit confused about kernel .config usage ? What does smatch needs?
I tried using multi_v7_defconfig and allmodefconfig, but everytime I try to:
$) make O=../my_build_dir CHECK="~/src/smatch/smatch -p=kernel" C=1
bzImage modules -j32
I get asked about config options again. As below:
*
* Restart config...
*
*
* General setup
*
Compile also drivers which will not load (COMPILE_TEST) [Y/n/?] y
Compile the kernel with warnings as errors (WERROR) [Y/n/?] y
Compile test UAPI headers (UAPI_HEADER_TEST) [N/y/?] (NEW)
...
Am I missing something ?
next reply other threads:[~2023-11-02 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 9:00 Umang Jain [this message]
2023-11-02 9:50 ` Kernel config usage Dan Carpenter
2023-11-02 11:21 ` Umang Jain
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=bfc8a5ff-7571-fbcd-2b1f-54af2571d133@ideasonboard.com \
--to=umang.jain@ideasonboard.com \
--cc=smatch@vger.kernel.org \
/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).