On Sun, Aug 12, 2012 at 3:09 AM, Rafi Rubin <r...@ugcs.caltech.edu> wrote:
> There were four patches in the set I tested (that fixed the problem).
>
> Commits:
> adad004e1a50f8c64d9f116cd4934da937b51e27
> 6795a524f0b049ceb5417d5036ab5e233345b900
> 61c91dd4a58b21a783e37208f4d02e3cb4b637c4
> 1cecc5cc0658e128bcad0b29edb96f286066571d
>
> I can confirm they are all in 3.6-rc1, and that it does in fact the rc works 
> fine.
>
> Now I get to find out if the other bugs that were keeping me at 3.5.0 have
> been fixed yet :)

My current kernel (based on 3.5.1) contains all those patches, yet
displays the problem.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to