From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: phind.uet@gmail.com, Kevin Wolf <kwolf@redhat.com>,
Hanna Reitz <hreitz@redhat.com>, Stefan Weil <sw@weilnetz.de>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] util: Move qemu_ftruncate64 from block/file-win32.c to oslib-win32.c
Date: Tue, 16 Dec 2025 15:00:32 -0800 [thread overview]
Message-ID: <345bee9e-4b3d-411c-9f45-eba47a72366e@linaro.org> (raw)
In-Reply-To: <20251215164512.322786-3-phind.uet@gmail.com>
On 12/15/25 8:45 AM, phind.uet@gmail.com wrote:
> From: Nguyen Dinh Phi <phind.uet@gmail.com>
>
> qemu_ftruncate64() is utility function that may be used outside of the block
> layer. Move it to util/oslib-win32.c where other Windows-specific utility
> functions reside.
>
> Signed-off-by: Nguyen Dinh Phi <phind.uet@gmail.com>
> ---
> block/file-win32.c | 32 --------------------------------
> util/oslib-win32.c | 34 ++++++++++++++++++++++++++++++++++
> 2 files changed, 34 insertions(+), 32 deletions(-)
Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
prev parent reply other threads:[~2025-12-16 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 16:45 [PATCH 0/2] Fix Windows build issues with newer MinGW phind.uet
2025-12-15 16:45 ` [PATCH 1/2] qga/vss-win32: Fix ConvertStringToBSTR redefinition " phind.uet
2025-12-16 6:26 ` Marc-André Lureau
2025-12-16 9:53 ` Kostiantyn Kostiuk
2025-12-17 18:13 ` Pierrick Bouvier
2025-12-16 23:00 ` Pierrick Bouvier
2025-12-15 16:45 ` [PATCH 2/2] util: Move qemu_ftruncate64 from block/file-win32.c to oslib-win32.c phind.uet
2025-12-15 17:33 ` Philippe Mathieu-Daudé
2025-12-16 23:00 ` Pierrick Bouvier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=345bee9e-4b3d-411c-9f45-eba47a72366e@linaro.org \
--to=pierrick.bouvier@linaro.org \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=phind.uet@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).