From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kbuild@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Tim Bird <tim.bird@am.sony.com>
Subject: Re: `make oldconfig' no longer updating `.config.old'?
Date: Mon, 4 Aug 2008 22:10:40 +0200 [thread overview]
Message-ID: <20080804201040.GA28982@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0808040857340.23329@anakin>
On Mon, Aug 04, 2008 at 09:02:43AM +0200, Geert Uytterhoeven wrote:
> Hi,
>
> I have the habit of doing `make .config{.old,}' after each config run,
> to see what was changed. But since a few weeks, `make oldconfig' no longer
> seems to update `.config.old'.
>
> This also breaks the default behavior of `scripts/diffconfig' (`If no
> config files are specified, .config and .config.old are used.').
>
> Was this change intentional?
.config is with current kconfig updated only if a user visible
symbol changes (or something like that).
I had another similar report where .config was not created if
missing and confi was not changed.
Fix is below and I will commit it soon.
Sam
diff --git a/scripts/kconfig/conf.c b/scripts/kconfig/conf.c
index 9fba838..36b5eed 100644
--- a/scripts/kconfig/conf.c
+++ b/scripts/kconfig/conf.c
@@ -596,7 +596,7 @@ int main(int ac, char **av)
break;
}
- if (conf_get_changed() && conf_write(NULL)) {
+ if (conf_write(NULL)) {
fprintf(stderr, _("\n*** Error during writing of the kernel configuration.\n\n"));
exit(1);
}
next prev parent reply other threads:[~2008-08-04 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 7:02 `make oldconfig' no longer updating `.config.old'? Geert Uytterhoeven
2008-08-04 20:10 ` Sam Ravnborg [this message]
2008-08-05 7:31 ` Geert Uytterhoeven
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=20080804201040.GA28982@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=geert@linux-m68k.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.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