All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] qapi/ui: Fix documentation of upper bound value in InputMoveEvent
@ 2025-01-16 10:44 Zhang Boyang
  2025-01-16 12:40 ` Markus Armbruster
  0 siblings, 1 reply; 4+ messages in thread
From: Zhang Boyang @ 2025-01-16 10:44 UTC (permalink / raw)
  To: qemu-devel; +Cc: Markus Armbruster, Zhang Boyang

The upper bound of pointer position in InputMoveEvent should be 0x7fff,
according to INPUT_EVENT_ABS_MAX.

Signed-off-by: Zhang Boyang <zhangboyang.id@gmail.com>
---
 qapi/ui.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/qapi/ui.json b/qapi/ui.json
index 460a26b981..7b18662018 100644
--- a/qapi/ui.json
+++ b/qapi/ui.json
@@ -1133,7 +1133,7 @@
 # @axis: Which axis is referenced by @value.
 #
 # @value: Pointer position.  For absolute coordinates the valid range
-#     is 0 -> 0x7ffff
+#     is 0 -> 0x7fff
 #
 # Since: 2.0
 ##
-- 
2.30.2



^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH] qapi/ui: Fix documentation of upper bound value in InputMoveEvent
  2025-01-16 10:44 [PATCH] qapi/ui: Fix documentation of upper bound value in InputMoveEvent Zhang Boyang
@ 2025-01-16 12:40 ` Markus Armbruster
  2025-01-16 12:43   ` Zhang Boyang
  0 siblings, 1 reply; 4+ messages in thread
From: Markus Armbruster @ 2025-01-16 12:40 UTC (permalink / raw)
  To: Zhang Boyang; +Cc: qemu-devel

Zhang Boyang <zhangboyang.id@gmail.com> writes:

> The upper bound of pointer position in InputMoveEvent should be 0x7fff,
> according to INPUT_EVENT_ABS_MAX.
>
> Signed-off-by: Zhang Boyang <zhangboyang.id@gmail.com>
> ---
>  qapi/ui.json | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/qapi/ui.json b/qapi/ui.json
> index 460a26b981..7b18662018 100644
> --- a/qapi/ui.json
> +++ b/qapi/ui.json
> @@ -1133,7 +1133,7 @@
>  # @axis: Which axis is referenced by @value.
>  #
>  # @value: Pointer position.  For absolute coordinates the valid range
> -#     is 0 -> 0x7ffff
> +#     is 0 -> 0x7fff

Opportunity to replace "->" by "to" or "..".  If you agree, I'll squash
that into your patch in my tree.

>  #
>  # Since: 2.0
>  ##

Acked-by: Markus Armbruster <armbru@redhat.com>



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] qapi/ui: Fix documentation of upper bound value in InputMoveEvent
  2025-01-16 12:40 ` Markus Armbruster
@ 2025-01-16 12:43   ` Zhang Boyang
  2025-01-16 13:51     ` Markus Armbruster
  0 siblings, 1 reply; 4+ messages in thread
From: Zhang Boyang @ 2025-01-16 12:43 UTC (permalink / raw)
  To: Markus Armbruster; +Cc: qemu-devel



On 2025/1/16 20:40, Markus Armbruster wrote:
> Zhang Boyang <zhangboyang.id@gmail.com> writes:
> 
>> The upper bound of pointer position in InputMoveEvent should be 0x7fff,
>> according to INPUT_EVENT_ABS_MAX.
>>
>> Signed-off-by: Zhang Boyang <zhangboyang.id@gmail.com>
>> ---
>>   qapi/ui.json | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/qapi/ui.json b/qapi/ui.json
>> index 460a26b981..7b18662018 100644
>> --- a/qapi/ui.json
>> +++ b/qapi/ui.json
>> @@ -1133,7 +1133,7 @@
>>   # @axis: Which axis is referenced by @value.
>>   #
>>   # @value: Pointer position.  For absolute coordinates the valid range
>> -#     is 0 -> 0x7ffff
>> +#     is 0 -> 0x7fff
> 
> Opportunity to replace "->" by "to" or "..".  If you agree, I'll squash
> that into your patch in my tree.
> 

OK, Thank you :)

Zhang Boyang

>>   #
>>   # Since: 2.0
>>   ##
> 
> Acked-by: Markus Armbruster <armbru@redhat.com>
> 



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH] qapi/ui: Fix documentation of upper bound value in InputMoveEvent
  2025-01-16 12:43   ` Zhang Boyang
@ 2025-01-16 13:51     ` Markus Armbruster
  0 siblings, 0 replies; 4+ messages in thread
From: Markus Armbruster @ 2025-01-16 13:51 UTC (permalink / raw)
  To: Zhang Boyang; +Cc: qemu-devel

Zhang Boyang <zhangboyang.id@gmail.com> writes:

> On 2025/1/16 20:40, Markus Armbruster wrote:
>> Zhang Boyang <zhangboyang.id@gmail.com> writes:
>> 
>>> The upper bound of pointer position in InputMoveEvent should be 0x7fff,
>>> according to INPUT_EVENT_ABS_MAX.
>>>
>>> Signed-off-by: Zhang Boyang <zhangboyang.id@gmail.com>
>>> ---
>>>   qapi/ui.json | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/qapi/ui.json b/qapi/ui.json
>>> index 460a26b981..7b18662018 100644
>>> --- a/qapi/ui.json
>>> +++ b/qapi/ui.json
>>> @@ -1133,7 +1133,7 @@
>>>   # @axis: Which axis is referenced by @value.
>>>   #
>>>   # @value: Pointer position.  For absolute coordinates the valid range
>>> -#     is 0 -> 0x7ffff
>>> +#     is 0 -> 0x7fff
>>
>> Opportunity to replace "->" by "to" or "..".  If you agree, I'll squash
>> that into your patch in my tree.
>> 
>
> OK, Thank you :)
>
> Zhang Boyang

Queued.  Thanks!

[...]



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2025-01-16 13:52 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-01-16 10:44 [PATCH] qapi/ui: Fix documentation of upper bound value in InputMoveEvent Zhang Boyang
2025-01-16 12:40 ` Markus Armbruster
2025-01-16 12:43   ` Zhang Boyang
2025-01-16 13:51     ` Markus Armbruster

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.