public inbox for linux-hyperv@vger.kernel.org
 help / color / mirror / Atom feed
From: yasuenag@gmail.com
To: eahariha@linux.microsoft.com
Cc: kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org,
	decui@microsoft.com, linux-hyperv@vger.kernel.org,
	ssengar@linux.microsoft.com,
	Yasumasa Suenaga <yasuenag@gmail.com>
Subject: [PATCH v3 0/1] hv_fcopy_uio_daemon: Fix file copy failure between Windows host and Linux guest
Date: Wed,  4 Jun 2025 08:42:59 +0900	[thread overview]
Message-ID: <20250603234300.1997-1-yasuenag@gmail.com> (raw)
In-Reply-To: <e174e3b0-6b62-4996-9854-39c84e10a317@linux.microsoft.com>

From: Yasumasa Suenaga <yasuenag@gmail.com>

Thanks a lot for your advice!
I fixed cosmetic problems and checked it with checkpatch.pl .
And also I fixed subject and description in the commit
as the document pointed.

I hope this version would go well...


Best regards,

Yasumasa


Yasumasa Suenaga (1):
  hv_fcopy_uio_daemon: Fix file copy failure between Windows host and
    Linux guest

 tools/hv/hv_fcopy_uio_daemon.c | 37 ++++++++++++++--------------------
 1 file changed, 15 insertions(+), 22 deletions(-)

-- 
2.49.0


  reply	other threads:[~2025-06-03 23:43 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
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       ` yasuenag [this message]
2025-06-03 23:43         ` [PATCH v3 1/1] hv_fcopy_uio_daemon: Fix file copy failure between Windows host and Linux guest 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=20250603234300.1997-1-yasuenag@gmail.com \
    --to=yasuenag@gmail.com \
    --cc=decui@microsoft.com \
    --cc=eahariha@linux.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