1a9b6d018SJoakim Bech<!-- 2a9b6d018SJoakim Bech General guidance when creating issues: 3a9b6d018SJoakim Bech 4a9b6d018SJoakim Bech 1. Please try to remember to close the issue when you have 5a9b6d018SJoakim Bech got an answer to your question. 6a9b6d018SJoakim Bech 7a9b6d018SJoakim Bech 2. It never hurts to state which commit or release tag you are using in case 8a9b6d018SJoakim Bech the question is about build issues. 9a9b6d018SJoakim Bech 10a9b6d018SJoakim Bech 3. Try to use GitHub markdown formatting to make your issue more readable: 11*ca0e80d7SJoakim Bech https://help.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#quoting-code 12a9b6d018SJoakim Bech 13a9b6d018SJoakim Bech 4. Try to search for the issue before posting the question: 14a9b6d018SJoakim Bech -> Issues tab -> Filters 15a9b6d018SJoakim Bech 16a9b6d018SJoakim Bech 5. Check the FAQ before posting a question: 17*ca0e80d7SJoakim Bech https://optee.readthedocs.io/en/latest/faq/faq.html 18a9b6d018SJoakim Bech 19a9b6d018SJoakim Bech NOTE: This comment will not be shown in the issue, so no harm keeping it, 20a9b6d018SJoakim Bech but feel free to remove it if you like. 21a9b6d018SJoakim Bech--> 22