From: yasuenag@gmail.com
To: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
decui@microsoft.com
Cc: linux-hyperv@vger.kernel.org, ssengar@linux.microsoft.com,
Yasumasa Suenaga <yasuenag@gmail.com>
Subject: [PATCH v2 0/1] Path string from the host should not be treated
Date: Tue, 3 Jun 2025 08:56:11 +0900 [thread overview]
Message-ID: <20250602235612.1542-1-yasuenag@gmail.com> (raw)
In-Reply-To: <82cbefe0-c9d0-457e-99dd-82842ee64cef@linux.microsoft.com>
From: Yasumasa Suenaga <yasuenag@gmail.com>
Hi,
Easwar, thanks a lot for your comment! I fixed where you pointed.
Let me know if something wrong in this patch - this is my first
contribution to Linux kernel...
Yasumasa Suenaga (1):
Path string from the host should not be treated as wchar_t
tools/hv/hv_fcopy_uio_daemon.c | 36 +++++++++++++---------------------
1 file changed, 14 insertions(+), 22 deletions(-)
--
2.49.0
next prev parent reply other threads:[~2025-06-02 23:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 13:45 [PATCH] Path string from the host should not be treated as wchar_t yasuenag
2025-06-02 16:39 ` Easwar Hariharan
2025-06-02 23:55 ` [PATCH v2 0/1] Path string from the host should not be treated yasuenag
2025-06-02 23:56 ` yasuenag [this message]
2025-06-02 23:56 ` [PATCH v2 1/1] Path string from the host should not be treated as wchar_t yasuenag
2025-06-03 21:26 ` [PATCH v2 0/1] Path string from the host should not be treated Easwar Hariharan
2025-06-03 23:42 ` [PATCH v3 0/1] hv_fcopy_uio_daemon: Fix file copy failure between Windows host and Linux guest yasuenag
2025-06-03 23:43 ` [PATCH v3 1/1] " yasuenag
2025-06-04 6:19 ` Naman Jain
2025-06-04 9:10 ` Yasumasa Suenaga
2025-06-04 12:36 ` Naman Jain
2025-06-04 13:12 ` Yasumasa Suenaga
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=20250602235612.1542-1-yasuenag@gmail.com \
--to=yasuenag@gmail.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=ssengar@linux.microsoft.com \
--cc=wei.liu@kernel.org \
/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