From: Kevin Wolf <kwolf@redhat.com>
To: "Hervé Poussineau" <hpoussin@reactos.org>
Cc: hreitz@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/2] Fix some problems with vvfat in R/W mode
Date: Fri, 21 Oct 2022 11:45:54 +0200 [thread overview]
Message-ID: <Y1JqUvv7hRIKQipt@redhat.com> (raw)
In-Reply-To: <20221010175511.3414357-1-hpoussin@reactos.org>
Am 10.10.2022 um 19:55 hat Hervé Poussineau geschrieben:
> Hi,
>
> When testing vvfat in read-write mode, I came across some blocking
> problems when using Windows guests.
> This patchset is not here to fix all problems of vvfat, but only the
> main ones I encountered.
>
> First patch allows setting/resetting the 'volume dirty' flag on
> boosector, and the second one allows creating file names with spaces.
>
> Hervé
>
> Changes since v1:
> - updated patch 1 with remarks (modify in-memory copy, add comment about
> FAT32)
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2022-10-21 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 17:55 [PATCH v2 0/2] Fix some problems with vvfat in R/W mode Hervé Poussineau
2022-10-10 17:55 ` [PATCH v2 1/2] vvfat: allow some writes to bootsector Hervé Poussineau
2022-10-10 17:55 ` [PATCH v2 2/2] vvfat: allow spaces in file names Hervé Poussineau
2022-10-21 9:45 ` Kevin Wolf [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=Y1JqUvv7hRIKQipt@redhat.com \
--to=kwolf@redhat.com \
--cc=hpoussin@reactos.org \
--cc=hreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).