Hi, I had to rebase ath6kl-next branch in ath6kl.git due to a commit immediately followed by a revert. Most likely our upstream maintainers don't like that so I wanted to avoid a publig flogging =) The downside is that some of the commit ids have changed. But master branch is unaffected, the users of master branch can still do 'git pull' and everything will just work. I also updated master branch to 3.7-rc2-wl. But don't even dream about using bisect on the master branch, the history on that branch is so ugly that it won't work. For bisect or checking the git history I recommend to use ath6kl-next branch. Kalle -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
