diff options
author | Paul Gortmaker <paul.gortmaker@windriver.com> | 2014-09-17 10:57:45 -0400 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-09-17 08:02:07 -0700 |
commit | 8ba4caf1ee1585f018d32ab924244c9589bc9f37 (patch) | |
tree | 7a8ef0926c99ebca9c4a67ee9cc1da3433d98c48 /arch/arc/Kconfig.debug | |
parent | 37504a3be90b69438426d74ccf467a9fe192932b (diff) | |
download | linux-8ba4caf1ee1585f018d32ab924244c9589bc9f37.tar.bz2 |
Revert "init: make rootdelay=N consistent with rootwait behaviour"
This reverts commit 4dfe694f616e00e6fd83e5bbcd7a3c4d7113493d.
In that, we did:
Here we move the rootdelay code to be right beside the rootwait code, so
that their behaviour is consistent.
...which is fine, but in hindsight, perhaps moving the rootwait to be
beside the rootdelay would have been better. We also indicated:
It should be noted that in doing so, the actions based on the
saved_root_name[0] and initrd_load() were previously put on hold by
rootdelay=N and now currently will not be delayed. However, I think
consistent behaviour is more important than matching historical behaviour
of delaying the above two operations.
But Pavel reported an instance where an ARM target with root on MMC
was failing to mount root, and Russell diagnosed it to the fact that
the call to set ROOT_DEV within the saved_root_name[0] processing
block mentioned above was no longer being delayed.
Rather than moving both wait clauses to the original position of
rootdelay and risking unearthing other possible corner case breakage
at this point in time, we simply revert now and we can revisit
trying the alternate/earlier location in another development cycle.
Cc: Pavel Machek <pavel@denx.de>
Cc: Russell King <linux@arm.linux.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/arc/Kconfig.debug')
0 files changed, 0 insertions, 0 deletions