This is an old revision of the document!
Go back –> ath10k
ath10k development happens in Kalle Valo's ath.git tree on kernel.org:
https://git.kernel.org/cgit/linux/kernel/git/kvalo/ath.git/
To clone the tree:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git
ath10k driver is located in directory drivers/net/wireless/ath/ath10k.
If you just want to browse the source code with your web browser this links always points to latest version of ath10k:
https://git.kernel.org/cgit/linux/kernel/git/kvalo/ath.git/tree/drivers/net/wireless/ath/ath10k
Periodically Kalle Valo merges ath-next and ath-current branches from ath.git into wireless-drivers-next and wireless-drivers tree, respectively. Then David Miller merges them to net-next and net trees, respectively, which are eventually merged by Linus Torvalds to the official kernel releases.
As a rough estimate it takes patches in ath-next 2-4 months to propagate from ath.git to the next official Linux release and patches from ath-current 1-3 weeks to propagate to the next -rc release.
See also submitting ath10k patches.
ath.git contains multiple branches:
To clarify the meaning with ath-current and ath-next let's take a concrete example: let's say that the latest release from Linux is v4.9-rc2. If a patch is applied to ath-current it will most like be in v4.9-rc4 or v4.9-rc5 (usually it takes a minimum of one week to get to Linus' tree, sometimes more). But if the patch is applied to ath-next the first it will be in v4.10-rc1.