We appreciate your contributions! Because this is an open source project, we want to keep it as easy as possible to contribute changes. However, we need contributors to follow a few guidelines.
There are a few architectural requirements that must be followed by contributed changes.
#ifdefs
for the target or HIC into common code.Contributed source code must match the existing style of the DAPLink code base.
The key requirements are:
_t
suffix.k
and use camel case, e.g. kHardwareReset
.For other style questions, please look to the existing code for answers.
By creating a pull request on GitHub, you are granting license your contributions under the same Apache 2.0 license as the original code. However, you still own the copyright to your contributions. You may add your copyright below the Arm copyright in the license header at the top of the source file. If a file is newly added by you, it must contain the standard license header, but it does not require an Arm copyright. Please note that we do not list changes in each source file by copyright owner, as this becomes a burden to maintain.
Please create a pull request in GitHub with your contribution. Before creating the pull request, please ensure that your code meets the requirements listed above and all tests pass. We also run the tests on a wide range of boards for every pull request using our CI setup. Changes must pass on all tested boards before the the pull request can be merged.
The developers' guide describes how to create your development environment. The automated tests guide provides information about the available types of tests and describes how to run the tests.
For more information about contributing, see the Mbed OS contributor documentation. Although this documentation is written primarily with Mbed OS in mind, much of it applies directly to DAPLink, as well.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。