make u-boot-ddr4-patch boardspecific #973
Merged
Conversation
|
Why are |
zador-blood-stained
added a commit
that referenced
this issue
May 24, 2018
|
I‘m sorry. Somehow I messed things up. I will be more careful in the future.
Christian
… Am 24.05.2018 um 21:26 schrieb Mikhail ***@***.***>:
Why are output and userpatches symlinks included in this PR and, most importantly, why was this merged without checking the changed files list?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
These patches are quite specific and broke u-boot on my z28pro.
It was stuck on:
...
DRAM:
...
I would be surprised, if the Rock64 is not affected.
The text was updated successfully, but these errors were encountered: