On Fri, Dec 15, 2017 at 1:16 AM, Samuel Thibault
wrote:
> Hello,
>
> Benjamin Tissoires, on jeu. 14 déc. 2017 14:25:20 +0100, wrote:
>> I marked them as stable as I believe eventhough not many
>> people discovered those and reported them, they should
>> still be
On Fri, Dec 15, 2017 at 1:16 AM, Samuel Thibault
wrote:
> Hello,
>
> Benjamin Tissoires, on jeu. 14 déc. 2017 14:25:20 +0100, wrote:
>> I marked them as stable as I believe eventhough not many
>> people discovered those and reported them, they should
>> still be fixed in current kernels.
>
>
Hello,
Benjamin Tissoires, on jeu. 14 déc. 2017 14:25:20 +0100, wrote:
> I marked them as stable as I believe eventhough not many
> people discovered those and reported them, they should
> still be fixed in current kernels.
Well, the quoted source lines are not in any stable tree, I don't even
Hello,
Benjamin Tissoires, on jeu. 14 déc. 2017 14:25:20 +0100, wrote:
> I marked them as stable as I believe eventhough not many
> people discovered those and reported them, they should
> still be fixed in current kernels.
Well, the quoted source lines are not in any stable tree, I don't even
Hi,
Peter wrote a fuzzing uinput program[1] to check on libinput,
and the result is that the kernel fails more often than
libinput :)
These 2 patches allow to fix the early failures.
I marked them as stable as I believe eventhough not many
people discovered those and reported them, they should
Hi,
Peter wrote a fuzzing uinput program[1] to check on libinput,
and the result is that the kernel fails more often than
libinput :)
These 2 patches allow to fix the early failures.
I marked them as stable as I believe eventhough not many
people discovered those and reported them, they should
6 matches
Mail list logo