Comment 23 for bug 1431473

Darn, I think I got lost in version numbers. While the change mentioned in comment #21 is causing the module load to fail, it cannot be helping to make this present in L1. Because 3.13 did work with a 3.16 kernel. It was only 3.2 that failed. And the change was in 3.15. So it is something else that causes both features to be set as supported in 3.13 but not in 3.2. Only before 3.15 this cannot be noticed.