From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] kbuild: include config.mk when auto.conf is not older than .config
Date: Fri, 03 Apr 2015 10:36:03 -0600 [thread overview]
Message-ID: <551EC173.1030304@wwwdotorg.org> (raw)
In-Reply-To: <1428031825-13573-1-git-send-email-yamada.masahiro@socionext.com>
On 04/02/2015 09:30 PM, Masahiro Yamada wrote:
> Since the Kconfig conversion, config.mk has been included only when
> include/config/auto.conf is newer than the .config file.
>
> It causes build error if both files have the same time-stamps.
> It is actually possible because EXT* file systems have a 1s time-stamp
> resolution.
>
> The config.mk should be included when include/config/auto.conf is
> *not older* than the .config file.
Tested-by: Stephen Warren <swarren@nvidia.com>
I ran a loop of 941 "MAKEALL rpi_2" during a meeting without issue. I
also applied the same patch to a tree that had the timestamps set in a
way that triggered the problem, and it immediately solved it there.
next prev parent reply other threads:[~2015-04-03 16:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 3:30 [U-Boot] [PATCH] kbuild: include config.mk when auto.conf is not older than .config Masahiro Yamada
2015-04-03 16:36 ` Stephen Warren [this message]
2015-04-07 17:59 ` [U-Boot] " Tom Rini
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=551EC173.1030304@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.