On 03.08.23 17:43, ThinerLogoer wrote:
At 2023-07-28 18:45:20, "David Hildenbrand" wrote:
Whatever you prefer! If I resend the patch, I would keep you the author
and only add my Co-authored-by: Signed-off-by:.
Just let me know.
Hello,
I wonder whether you have planned to resubmit the cur
At 2023-07-28 18:45:20, "David Hildenbrand" wrote:
>
>
>Whatever you prefer! If I resend the patch, I would keep you the author
>and only add my Co-authored-by: Signed-off-by:.
>
>Just let me know.
>
Hello,
I wonder whether you have planned to resubmit the current patch anytime soon,
or is it
At 2023-07-28 18:45:20, "David Hildenbrand" wrote:
>>> Quick untested attempt to move retry handling to the caller:
>>>
>>> diff --git a/softmmu/physmem.c b/softmmu/physmem.c
>>> index 3df73542e1..c826bb78fc 100644
>>> --- a/softmmu/physmem.c
>>> +++ b/softmmu/physmem.c
>>> @@ -1289,8 +1289,7 @@ s
On 28.07.23 07:46, ThinerLogoer wrote:
Sorry my mail agent just have a bug
No worries :)
At 2023-07-28 02:30:09, "David Hildenbrand" wrote:
On 27.07.23 17:20, ThinerLogoer wrote:
At 2023-07-27 21:18:44, "David Hildenbrand" wrote:
On 26.07.23 16:59, Thiner Logoer wrote:
Users may give
Sorry my mail agent just have a bug
At 2023-07-28 02:30:09, "David Hildenbrand" wrote:
>On 27.07.23 17:20, ThinerLogoer wrote:
>>
>> At 2023-07-27 21:18:44, "David Hildenbrand" wrote:
>>> On 26.07.23 16:59, Thiner Logoer wrote:
Users may give "-mem-path" a read only file and expect the fil
At 2023-07-28 02:30:09, "David Hildenbrand" wrote:
>On 27.07.23 17:20, ThinerLogoer wrote:
>>
>> At 2023-07-27 21:18:44, "David Hildenbrand" wrote:
>>> On 26.07.23 16:59, Thiner Logoer wrote:
Users may give "-mem-path" a read only file and expect the file
to be mapped r
On 27.07.23 17:20, ThinerLogoer wrote:
At 2023-07-27 21:18:44, "David Hildenbrand" wrote:
On 26.07.23 16:59, Thiner Logoer wrote:
Users may give "-mem-path" a read only file and expect the file
to be mapped read-write privately. Allow this but give a warning
since other users may surprise whe
At 2023-07-27 21:18:44, "David Hildenbrand" wrote:
>On 26.07.23 16:59, Thiner Logoer wrote:
>> Users may give "-mem-path" a read only file and expect the file
>> to be mapped read-write privately. Allow this but give a warning
>> since other users may surprise when the ram file is readonly and
>>
On 26.07.23 16:59, Thiner Logoer wrote:
Users may give "-mem-path" a read only file and expect the file
to be mapped read-write privately. Allow this but give a warning
since other users may surprise when the ram file is readonly and
qemu suddenly aborts elsewhere.
Suggested-by: David Hildenbran
Users may give "-mem-path" a read only file and expect the file
to be mapped read-write privately. Allow this but give a warning
since other users may surprise when the ram file is readonly and
qemu suddenly aborts elsewhere.
Suggested-by: David Hildenbrand
Signed-off-by: Thiner Logoer
---
See
10 matches
Mail list logo
