Bug#1012655: upstream bug and fix

2022-06-15 Thread Salvatore Bonaccorso 
Hi,

On Wed, Jun 15, 2022 at 07:59:27PM +0200, Diederik de Haas wrote:
> On Wednesday, 15 June 2022 17:40:45 CEST Stephan Verbücheln wrote:
> > Kernel 5.18.4 got the patch.
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/driver
> > s/input/mouse/bcm5974.c?id=v5.18.4=v5.18.3
> 
> Excellent, thanks for mentioning that :-)
> 
> > I will just use 5.17 or external mouse until the fix lands in Sid.
> 
> My guess is that the next upload to Sid should have it then.

This assumption is correct :)

Regards,
Salvatore

Bug#1012655: upstream bug and fix

2022-06-15 Thread Diederik de Haas 
On Wednesday, 15 June 2022 17:40:45 CEST Stephan Verbücheln wrote:
> Kernel 5.18.4 got the patch.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/driver
> s/input/mouse/bcm5974.c?id=v5.18.4=v5.18.3

Excellent, thanks for mentioning that :-)

> I will just use 5.17 or external mouse until the fix lands in Sid.

My guess is that the next upload to Sid should have it then.

signature.asc
Description: This is a digitally signed message part.

Bug#1012655: upstream bug and fix

2022-06-15 Thread Stephan Verbücheln 
Kernel 5.18.4 got the patch.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/drivers/input/mouse/bcm5974.c?id=v5.18.4=v5.18.3

Regards

Bug#1012655: upstream bug and fix

2022-06-12 Thread Stephan Verbücheln 
They merged it (on June 7) into kernel 5.19, but kernel 5.18.3
(released June 9) does not seem to have it yet.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/?id=v5.18.3=v5.18=2

I will just use 5.17 or external mouse until the fix lands in Sid.

Thank you and regards

Bug#1012655: upstream bug and fix

2022-06-11 Thread Diederik de Haas 
Control: tag -1 fixed-upstream

On Saturday, 11 June 2022 09:33:09 CEST Stephan Verbücheln wrote:
> I found an upstream report which has matching symptoms.
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=215890
> 
> However, there is confusion about the resolution. One reply states that
> it was resolved in 5.18.0, but other replies talk about accidental fixes.
> 
> A fix was submitted more recently than 5.18.0 release:
> https://lore.kernel.org/all/20220606113636.588955-1-mathias.ny...@linux.inte
> l.com/

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c42e65664390be7c1ef3838cd84956d3a2739d60
is where it is fixed. But there is indeed some confusion as noted by Linus:
https://lore.kernel.org/all/CAHk-=wjcc15lsps1nj-e5nc-hr3ogvy+bqumyld9vz4hzad...@mail.gmail.com/

I normally use https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
and if you search for the primary commit message, it doesn't find it.
If you add "commit/?id=c42e65664390be7c1ef3838cd84956d3a2739d60" to that base
URL, you'll see "Notice: this object is not reachable from any branch."

So it is fixed upstream and according to Linus it is also part of 5.19-rc1
Apparently it's considered an important fix, so I guess it should be backported
to 5.18 'shortly'.

signature.asc
Description: This is a digitally signed message part.

Bug#1012655: upstream bug and fix

2022-06-11 Thread Stephan Verbücheln 
When I filed the bug, I could not find any other reports. Now I found
an upstream report which has matching symptoms.

https://bugzilla.kernel.org/show_bug.cgi?id=215890

However, there is confusion about the resolution. One reply states that
it was resolved in 5.18.0, but other replies talk about accidental
fixes.

A fix was submitted more recently than 5.18.0 release:
https://lore.kernel.org/all/20220606113636.588955-1-mathias.ny...@linux.intel.com/

Regards