Fixed
Created: Dec 30, 2014
Updated: Sep 8, 2018
Resolved Date: Jan 23, 2015
Found In Version: 7.0
Fix Version: 7.0.0.2
Severity: Standard
Applicable for: Wind River Linux 7
Component/s: Kernel
An attempt was made to add the upstream commit for arm64 HAVE_ARCH_KGDB twice.
The 1st addition misplaced it at the end of the list, and the 2nd addition placed it correctly.
however, upon merging, the 2nd instance got transformed incorrectly from an addition into a relocation from the incorrect spot to the correct spot, making a patch that looked nonsensical when compared to what it claimed to do in its own commit log.
I have fixed all of this in the kenel-cache as can be seen here:
http://ala-git.wrs.com/cgit/kernel-cache/commit/?h=WRLINUX_7_0_HEAD&id=22a6a6c851e33e162c44cf95e3b09be3ae22f99e
However, in the fast forward tree, that leaves all branches that use standard/base (but not arm64 feature) with only the 1st of the two commits, and hence still having the mislocation.
While the mislocation is largely cosmetic, it will be a nuisance as we deploy automated comparisons of the ff tree with the "from-scratch" newly generated tree.
The attached commit against standard/base can be applied to that branch in the ff tree and merged out to all containing BSPs in order to help reduce the noise and false positives seen while running the auto comparisons.
