From: Kevin Wolf <kwolf@redhat.com>
To: "Clément Chigot" <chigot@adacore.com>
Cc: qemu-devel@nongnu.org, hreitz@redhat.com, qemu-block@nongnu.org
Subject: Re: [PATCH 2/5] vvfat: move fat_type check prior to size setup
Date: Thu, 23 Oct 2025 20:39:53 +0200 [thread overview]
Message-ID: <aPp2eRW7gQfv4hT7@redhat.com> (raw)
In-Reply-To: <20250903075721.77623-3-chigot@adacore.com>
Am 03.09.2025 um 09:57 hat Clément Chigot geschrieben:
> This allows to handle the default FAT size in a single place and make the
> following part taking care only about size parameters. It will be later
> moved away in a specific function.
>
> Setting a floppy disk of 1MB is no longer possible as it was a side
> effect of passing "fat-type=12". To be precise there were three cases:
> - fat-type undefined (aka default): a fat12 2MB disk
> - fat-type=16: a fat16 2Mb disk
> - fat-type=12: a fat12 1Mb disk
That's quite a strange interface!
If we're touching it anyway, I would change it to make the more common
format (1.44 MB) the default for FAT12 and make the 2.88 MB FAT12 floppy
temporarily unavailable and later require an explicit size. This way
both sizes would still be available using the fat-type.
Please say 1.44 MB and 2.88 MB in the commit message rather than 1MB (or
even 1Mb, which might mean megabit). There were other sizes like 1.2 MB
that are closer to 1 MB, so it's better to avoid that confusion.
> Now, that fat-type undefined means fat-type=2, it's no longer possible
s/2/12/
> to make that size distinction. It will be added back a bit later,
> through the size parameter.
>
> Signed-off-by: Clément Chigot <chigot@adacore.com>
The code looks good, apart from the change I suggested above (making
1.44 MB the default for FAT12).
Kevin
next prev parent reply other threads:[~2025-10-23 18:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 7:57 [PATCH 0/5] block/vvfat: introduce "size" option Clément Chigot
2025-09-03 7:57 ` [PATCH 1/5] vvfat: introduce no-mbr option Clément Chigot
2025-10-23 18:20 ` Kevin Wolf
2025-10-29 8:37 ` Clément Chigot
2025-10-29 10:56 ` Kevin Wolf
2025-10-29 13:44 ` Clément Chigot
2025-09-03 7:57 ` [PATCH 2/5] vvfat: move fat_type check prior to size setup Clément Chigot
2025-10-23 18:39 ` Kevin Wolf [this message]
2025-10-29 13:48 ` Clément Chigot
2025-10-29 13:58 ` BALATON Zoltan
2025-10-29 16:05 ` Kevin Wolf
2025-09-03 7:57 ` [PATCH 3/5] vvfat: add a define for SECTOR_SIZE Clément Chigot
2025-10-23 18:47 ` Kevin Wolf
2025-09-03 7:57 ` [PATCH 4/5] vvfat: move size parameters within driver structure Clément Chigot
2025-09-03 7:57 ` [PATCH 5/5] vvfat: add support for "size" options Clément Chigot
2025-10-23 19:29 ` Kevin Wolf
2025-10-24 8:30 ` Markus Armbruster
2025-10-24 9:23 ` Clément Chigot
2025-10-27 12:09 ` Markus Armbruster
2025-10-28 14:54 ` Clément Chigot
2025-10-31 7:46 ` Markus Armbruster
2025-10-31 9:47 ` Clément Chigot
2025-10-31 11:56 ` Kevin Wolf
2025-10-31 13:07 ` Clément Chigot
2025-11-05 7:06 ` Markus Armbruster
2025-11-05 7:08 ` Markus Armbruster
2025-11-05 9:35 ` Kevin Wolf
2025-11-05 10:15 ` Clément Chigot
2025-11-07 8:06 ` Markus Armbruster
2025-09-15 8:47 ` [PATCH 0/5] block/vvfat: introduce "size" option Clément Chigot
2025-10-07 7:43 ` Clément Chigot
2025-11-12 12:38 ` Richard W.M. Jones
2025-11-12 13:09 ` Clément Chigot
2025-11-13 8:41 ` Kevin Wolf
2025-11-13 9:13 ` Richard W.M. Jones
2025-11-13 13:13 ` Kevin Wolf
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=aPp2eRW7gQfv4hT7@redhat.com \
--to=kwolf@redhat.com \
--cc=chigot@adacore.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.