This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
en:users:drivers:ath10k:sources [2016/01/22 11:14] Kalle Valo ath.git is in kernel.org now |
en:users:drivers:ath10k:sources [2017/02/19 13:56] Kalle Valo [Submitting patches] Add link to a page about ath10k-check |
||
---|---|---|---|
Line 47: | Line 47: | ||
* If others have reported the issue commit log SHOULD use Reported-by: and Tested-by: tags. | * If others have reported the issue commit log SHOULD use Reported-by: and Tested-by: tags. | ||
* SHOULD be checkpatch clean: | * SHOULD be checkpatch clean: | ||
- | * FIXME: add checkpatch example with correct arguments | ||
* Patches SHOULD be sent with git send-email tool. | * Patches SHOULD be sent with git send-email tool. | ||
* Patchsets SHOULD contain no more than 12 patches. | * Patchsets SHOULD contain no more than 12 patches. | ||
* Patches SHOULD follow [[en/users/Drivers/ath10k/CodingStyle|ath10k coding style]] | * Patches SHOULD follow [[en/users/Drivers/ath10k/CodingStyle|ath10k coding style]] | ||
+ | * It's RECOMMENDED to test patches with [[en/users/Drivers/ath10k/CodingStyle#checking_code|ath10k-check]] | ||
The terminology is from [[http://www.ietf.org/rfc/rfc2119.txt|http://www.ietf.org/rfc/rfc2119.txt]] | The terminology is from [[http://www.ietf.org/rfc/rfc2119.txt|http://www.ietf.org/rfc/rfc2119.txt]] | ||
Line 72: | Line 72: | ||
* ath-next : Based on John's wireless-next tree and John will pull from this branch. ath6kl/ath10k patches are commited to this branch first and then merged to the master branch. For bisect runs it's better to use this branch instead of the master branch. | * ath-next : Based on John's wireless-next tree and John will pull from this branch. ath6kl/ath10k patches are commited to this branch first and then merged to the master branch. For bisect runs it's better to use this branch instead of the master branch. | ||
* pending : Used for building and runtime testing patches under review. Is rebased almost daily and hence commit ids are NOT stable. Use this only if you know what you are doing. | * pending : Used for building and runtime testing patches under review. Is rebased almost daily and hence commit ids are NOT stable. Use this only if you know what you are doing. | ||
+ | * master-pending : The pending branch merged on top of the master, for easier testing of the pending patches. Same rules apply as with the pending branch. |