kvalo at qca.qualcomm.com
Mon Jun 2 11:19:00 PDT 2014
as I start to send patches also to -rc releases there's a small change
in ath10k git branches:
I have a new branch ath-current which is for fixes going to the
"current" kernel version under development, for example currently that
means 3.16 which development will soon start. The ath-current branch
will contain only very important fixes we want to have in the next -rc
ath-next branch will continue be the main location for new ath10k
patches. All new features and most of the bugfixes go into this branch.
In practise these branches are transparate to ath10k developers and
users. Just continue using the master branch as I merge both ath-current
and ath-next branches into the master branch, just as before. But if you
used ath-next branch for something before, now make sure to check also
ath-current for important fixes. They will not be in ath-next branch.
More information about the ath10k