platforms/iq-615-evk: Add contents.xml.in#126
Conversation
Head branch was pushed to by a user without write access
|
Why is checksum update a separate commit? |
To keep it separate from the actual change. |
Without the checksum update the tree is broken. Don't create broken commits, they break |
Agreed, makes sense will squash the two commits. |
954770d to
cb3448e
Compare
|
Why is the contents.xml.in changes are changing so many hashes? Are you using the same PTOOL_SEED used by our CI (qcom-ptool-ci)? |
cb3448e to
83eb8c5
Compare
I had not done earlier. Now, after using PTOOL_SEED and compiled, checksum shows only the added files.
Maybe the instruction to run before pushing the change can be added to the README.md or CONTRIBUTING.md file. |
Add contents.xml.in file for IQ-615-EVK board. Add it to both emmc and ufs. This helps Axiom to run successfully end to end. Also update the integration test checksum manifest. Signed-off-by: Azhar Shaikh <azhashai@qti.qualcomm.com>
83eb8c5 to
635178c
Compare
Please open the PR updating |
Sure will do! |
Please help review: #128 |
Add contents.xml.in file for IQ-615-EVK board. Add it to both emmc and ufs. This helps Axiom to run successfully end to end.