From: Michal Marek <mmarek@suse.cz>
To: liguang <lig.fnst@cn.fujitsu.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][update] Makefile: allow no update .config build
Date: Fri, 29 Mar 2013 10:12:25 +0100 [thread overview]
Message-ID: <51555AF9.4020009@suse.cz> (raw)
In-Reply-To: <1364517997-24067-1-git-send-email-lig.fnst@cn.fujitsu.com>
On 29.3.2013 01:46, liguang wrote:
> if we pull some commits from other git repo
> which bring in a few CONFIG_* options, then
> we have to build all again, but we do assure
> these options are not interesting for us,
> so the long waiting build will be offending.
> this change help us to avoid all-build.
scripts/basic/fixdep makes sure that only the affected parts are rebuild
when the config changes. Obviously, if a CONFIG_ option appears in a
widely used header file, the whole kernel is rebuilt. Otherwise object
files would be built with different versions of the header file. If you
want to shoot yourself in the foot and override this, then do a 'touch
include/config/*.conf', but please do not add such a hack to the Makefile.
Michal
prev parent reply other threads:[~2013-03-29 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 0:46 [PATCH][update] Makefile: allow no update .config build liguang
2013-03-29 9:12 ` Michal Marek [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=51555AF9.4020009@suse.cz \
--to=mmarek@suse.cz \
--cc=lig.fnst@cn.fujitsu.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@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