From: Sam Ravnborg <sam@ravnborg.org>
To: m silverstri <michael.j.silverstri@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: How to run sparse tool?
Date: Thu, 13 Mar 2014 22:23:49 +0100 [thread overview]
Message-ID: <20140313212349.GA6326@ravnborg.org> (raw)
In-Reply-To: <CABMudhQt1B6kanw+u7A1yPnux-wUYGYq07qwFs4hGYhgdbYLTA@mail.gmail.com>
On Thu, Mar 13, 2014 at 11:54:13AM -0700, m silverstri wrote:
> Thanks. 'make allmodconfig' works.
> But before your answer, I am able to build and there is a .config
> file. But why 'make C=2 drivers/staging/wlan-ng/' decide to build
> config again ?
No idea.
Maybe "make V=1" or "make V=2" can give a hint.
Something triggers the re-run of the config which is usual because soem Kconfig files are touched, or .config.
Sam
prev parent reply other threads:[~2014-03-13 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 16:49 How to run sparse tool? m silverstri
2014-03-13 18:00 ` Sam Ravnborg
2014-03-13 18:54 ` m silverstri
2014-03-13 21:23 ` Sam Ravnborg [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=20140313212349.GA6326@ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-sparse@vger.kernel.org \
--cc=michael.j.silverstri@gmail.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).