[PATCH 2/6] win32u: Move WM_SETCURSOR implementation from user32.

[Marvin]

Hi,

It looks like your patch introduced the new failures shown below.
Please investigate and fix them before resubmitting your patch.
If they are not new, fixing them anyway would help a lot. Otherwise
please ask for the known failures list to be updated.

The tests also ran into some preexisting test failures. If you know how
to fix them that would be helpful. See the TestBot job for the details:

The full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=117143

Your paranoid android.


=== debian11 (32 bit report) ===

user32:
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 5: the msg 0x0135 was expected, but got msg 0x030f instead
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 7: the msg 0x8000 was expected, but got msg 0x0086 instead
msg.c:6881: Test failed: SetFocus(hwnd) on a button: 8: the msg sequence is not complete: expected 0000 - actual 0006
win.c:11770: Test succeeded inside todo block: child should be topmost
win.c:11773: Test failed: grandchild should be topmost
win.c:11781: Test failed: child should NOT be topmost
win.c:11784: Test succeeded inside todo block: grandchild should NOT be topmost
win.c:11787: Test failed: 007200BA: expected NOT topmost
win.c:11606: Test succeeded inside todo block: 5: hwnd 014F0052 is still topmost