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 [2015/09/02 12:19] Kalle Valo Add link to SubmittingPatches |
en:users:drivers:ath10k:sources [2017/02/19 13:56] Kalle Valo [Submitting patches] Add link to a page about ath10k-check |
||
---|---|---|---|
Line 3: | Line 3: | ||
+ | ===== ath10k sources location ===== | ||
+ | //ath10k// development happens in Kalle Valo's ath.git tree on kernel.org: | ||
- | ===== ath10k sources location ===== | + | https://git.kernel.org/cgit/linux/kernel/git/kvalo/ath.git/ |
- | + | ||
- | //ath10k// development happens in Kalle Valo's ath.git tree on github.com: | + | |
- | * [[https://github.com/kvalo/ath|https://github.com/kvalo/ath]] | + | |
To clone the tree: | To clone the tree: | ||
+ | <code>git clone git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git</code> | ||
- | <code>git clone https://github.com/kvalo/ath</code> | ||
ath10k driver is located in directory drivers/net/wireless/ath/ath10k. | ath10k driver is located in directory drivers/net/wireless/ath/ath10k. | ||
- | |||
- | If you can't use git, it's also possible to download .zip file from this link: | ||
- | * [[https://github.com/kvalo/ath/archive/master.zip|https://github.com/kvalo/ath/archive/master.zip]] | ||
If you just want to browse the source code with your web browser this links always points to latest version of ath10k: | If you just want to browse the source code with your web browser this links always points to latest version of ath10k: | ||
- | [[https://github.com/kvalo/ath/tree/master/drivers/net/wireless/ath/ath10k|https://github.com/kvalo/ath/tree/master/drivers/net/wireless/ath/ath10k]] | + | https://git.kernel.org/cgit/linux/kernel/git/kvalo/ath.git/tree/drivers/net/wireless/ath/ath10k |
Periodically Kalle Valo pulls the ath tree into wireless-drivers-next tree. Then David Miller pulls it to net-next which is eventually pulled by Linus Torvalds to official kernel releases. As a rough estimate it takes 2-4 months for a patch to propage from ath.git to an official Linux release. | Periodically Kalle Valo pulls the ath tree into wireless-drivers-next tree. Then David Miller pulls it to net-next which is eventually pulled by Linus Torvalds to official kernel releases. As a rough estimate it takes 2-4 months for a patch to propage from ath.git to an official Linux release. | ||
Line 51: | 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 76: | 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. |