Can someone use "git bisect" to find what commited introduce this bug in Kernel? http://kerneltrap.org/node/11753
I think that it happening in 2.6.22, so is necessary use bisect in 2.6.21 and 2.6.22
I really don't have time enough to do this.
Best regards, Renato
Can someone use "git bisect" to find what commited introduce this bug in Kernel? kerneltrap. org/node/ 11753
http://
I think that it happening in 2.6.22, so is necessary use bisect in 2.6.21 and 2.6.22
I really don't have time enough to do this.
Best regards,
Renato