From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: nicolas.pitre@linaro.org, linux@arm.linux.org.uk,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm: add default value for PHYS_OFFSET Kconfig setting
Date: Thu, 01 Dec 2011 14:52:10 +0400 [thread overview]
Message-ID: <4ED75C5A.4070508@ru.mvista.com> (raw)
In-Reply-To: <1322711557-8279-1-git-send-email-paul.gortmaker@windriver.com>
Hello.
On 01.12.2011 7:52, Paul Gortmaker wrote:
> Commit 1b9f95f8ade9efc2bd49f0e7b9dc61a038ac3eef introduced the new
Please also cite that commit's summary in parens.
> Kconfig for PHYS_OFFSET but it did not specify a default value.
> This has the undesired side effect of breaking an implictly used
> trick for updating defconfigs on the fly for routine buildtesting
> across all arch and all platforms, i.e.
> cp /path/to/somedefconfig .config ; yes "" | make oldconfig
> In particular, the at91x40_defconfig will enter an infinite loop
> with the above, since there is no default value, and conf will just
> keep asking for one, and "yes" will keep feeding in a line return.
> Signed-off-by: Paul Gortmaker<paul.gortmaker@windriver.com>
WBR, Sergei
next prev parent reply other threads:[~2011-12-01 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 3:52 Paul Gortmaker
2011-12-01 10:52 ` Sergei Shtylyov [this message]
2011-12-01 14:19 ` Arnd Bergmann
2011-12-02 4:38 ` Paul Gortmaker
2011-12-02 5:19 ` Nicolas Pitre
2011-12-02 5:33 ` Nicolas Pitre
2011-12-02 9:21 ` Uwe Kleine-König
2011-12-02 16:31 ` Paul Gortmaker
2011-12-02 19:07 ` Uwe Kleine-König
2011-12-02 19:27 ` Nicolas Pitre
2011-12-02 20:23 ` [PATCH] ARM: determine PHYS_OFFSET automatically for no-mmu configs Uwe Kleine-König
2011-12-02 22:19 ` Nicolas Pitre
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=4ED75C5A.4070508@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.pitre@linaro.org \
--cc=paul.gortmaker@windriver.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
Powered by JetHome