From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE
Date: Thu, 28 Jan 2016 17:42:41 +0000 [thread overview]
Message-ID: <20160128174241.GN10826@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160128031435.GA25625@wfg-t540p.sh.intel.com>
On Thu, Jan 28, 2016 at 11:14:35AM +0800, Fengguang Wu wrote:
> On Wed, Jan 27, 2016 at 10:44:01AM +0100, Arnd Bergmann wrote:
> > - CONFIG_PHYS_OFFSET needs to be entered manually to be a number
> > in 'make config'
>
> That's a problem for auto tests.
I'm really against the idea of providing some kind of "default" to it.
Not providing a default means that people _have_ to do some research
for their particular system in order to provide a value, and they're
more likely to get the right value. Providing a default will lead to
the assumption that the value is okay, and then we'll end up with
people complaining that their kernel doesn't boot, and is totally
silent.
The only default I'd accept is one based on the rest of the config -
in other words, re-introducing all the physical address of RAM that
we used to have in the mach/memory.h files...
There's other ways around these kinds of things, the Kconfig system
does allow a Kconfig fragment which can be used to pre-set some
configuration options to particular values - and so which can be used
to set CONFIG_PHYS_OFFSET prior to an allrandconfig or similar.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-01-28 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <569e1dbb.MgLv8OaZwklOxxtU%fengguang.wu@intel.com>
[not found] ` <1947556.38OyJnvGS5@wuerfel>
[not found] ` <20160127093018.GA21190@wfg-t540p.sh.intel.com>
2016-01-27 9:44 ` [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE Arnd Bergmann
2016-01-28 3:14 ` Fengguang Wu
2016-01-28 12:07 ` Arnd Bergmann
2016-01-28 17:42 ` Russell King - ARM Linux [this message]
2016-01-28 23:07 ` Arnd Bergmann
2016-01-29 8:01 ` Geert Uytterhoeven
2016-01-29 20:44 ` Arnd Bergmann
2016-01-29 21:24 ` Geert Uytterhoeven
2016-01-29 21:54 ` Arnd Bergmann
2016-01-29 23:15 ` Russell King - ARM Linux
2016-01-29 21:46 ` Russell King - ARM Linux
2016-01-28 18:00 ` 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=20160128174241.GN10826@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).