[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 2/4] Avoid multiple definitions of copy_file_range
|
From: |
Manolo de Medici |
|
Subject: |
Re: [PATCH 2/4] Avoid multiple definitions of copy_file_range |
|
Date: |
Wed, 17 Jan 2024 16:08:34 +0100 |
Understood, but I cannot judge if it is a bug in qemu or it fixes
another host os,
since qemu doesn't target only glibc.
In order to avoid breaking other hosts, I consider it more cautious to
ignore the difference.
In the long term the Hurd is going to implement copy_file_range
- [PATCH 2/4] Avoid multiple definitions of copy_file_range, Manolo de Medici, 2024/01/17
- Re: [PATCH 2/4] Avoid multiple definitions of copy_file_range, Philippe Mathieu-Daudé, 2024/01/17
- Re: [PATCH 2/4] Avoid multiple definitions of copy_file_range, Manolo de Medici, 2024/01/17
- Re: [PATCH 2/4] Avoid multiple definitions of copy_file_range, Samuel Thibault, 2024/01/17
- Re: [PATCH 2/4] Avoid multiple definitions of copy_file_range, Manolo de Medici, 2024/01/17
- Re: [PATCH 2/4] Avoid multiple definitions of copy_file_range, Samuel Thibault, 2024/01/17
- Re: [PATCH 2/4] Avoid multiple definitions of copy_file_range,
Manolo de Medici <=
- Re: [PATCH 2/4] Avoid multiple definitions of copy_file_range, Samuel Thibault, 2024/01/17
- Re: [PATCH 2/4] Avoid multiple definitions of copy_file_range, Manolo de Medici, 2024/01/17