Hi Keith,
Paul Menzel wrote:
https://review.coreboot.org/plugins/gitiles/board-status/+/71278e2819996f2e6...
Keith Emery wrote:
It’s in the path name or logs in the directory I referenced: 4.13-917-g192177d34d refers to commit hash 192177d34d.
I've tried both hash's refrencing both sucessfull builds for F2A85-M board. I just get:
error: pathspec '192177d34d' did not match any file(s) known to git error: pathspec 'fdfc473380' did not match any file(s) known to git
192177d34d is the commit locally on idwer's system at the time of testing - it's possible that he had some minor changes on top of the upstream code, resulting in a new commit.
Fortunately, this file:
https://review.coreboot.org/plugins/gitiles/board-status/+/71278e2819996f2e6...
Shows:
Upstream revision: 9a1b720b1f
And commit 9a1b720b1f is indeed some 950 commits ahead of the 4.13 tag, so I would try that out.
Kind regards
//Peter