From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Fabio D'Urso <fdurso@google.com>, qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH] hw/usb/dev-mtp: Correctly report free space
Date: Tue, 18 Jun 2024 17:40:30 +0200 [thread overview]
Message-ID: <d37c8eb0-afd2-45e2-a775-785f08987c3f@linaro.org> (raw)
In-Reply-To: <20240618003657.3344685-1-fdurso@google.com>
On 18/6/24 02:36, Fabio D'Urso wrote:
> In order to compute the amount of free space (in bytes), the number
> of available blocks (f_bavail) should be multiplied by the block
> size (f_frsize) instead of the total number of blocks (f_blocks).
>
> Signed-off-by: Fabio D'Urso <fdurso@google.com>
> ---
> hw/usb/dev-mtp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Patch queued, thanks!
prev parent reply other threads:[~2024-06-18 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 0:36 [PATCH] hw/usb/dev-mtp: Correctly report free space Fabio D'Urso
2024-06-18 4:27 ` Philippe Mathieu-Daudé
2024-06-18 15:40 ` Philippe Mathieu-Daudé [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=d37c8eb0-afd2-45e2-a775-785f08987c3f@linaro.org \
--to=philmd@linaro.org \
--cc=fdurso@google.com \
--cc=kraxel@redhat.com \
--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).