From: Bandan Das <bsd@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Bug 1798780 <1798780@bugs.launchpad.net>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] usb-mtp: replace the homebrew write with qemu_write_full
Date: Thu, 24 Jan 2019 03:19:03 -0500 [thread overview]
Message-ID: <jpg4l9yzcw8.fsf@linux.bootlegged.copy> (raw)
In-Reply-To: <20190124080137.2upct7emowdj7n2r@sirius.home.kraxel.org> (Gerd Hoffmann's message of "Thu, 24 Jan 2019 09:01:37 +0100")
Gerd Hoffmann <kraxel@redhat.com> writes:
> On Tue, Jan 22, 2019 at 07:41:16AM -0500, Bandan Das wrote:
>>
>> qemu_write_full takes care of partial blocking writes,
>> as in cases of larger file sizes
>>
>> Suggested-by: Peter Maydell <peter.maydell@linaro.org>
>> Signed-off-by: Bandan <bsd@redhat.com>
>
> Hmm, doesn't apply, and git fails to do a 3way merge too due to unknown
> sha1.
>
Oops, sorry, I realize now this is on top of the write buffer breakup patches.
Should I resend a v2 on top of master and send a v3 for the write buffer breakup
patches ?
> cheers,
> Gerd
next prev parent reply other threads:[~2019-01-24 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 9:07 [Qemu-devel] [Bug 1798780] [NEW] hw/usb/dev-mtp.c:1616: bad test ? dcb
2019-01-18 17:18 ` Peter Maydell
2019-01-22 12:38 ` Bandan Das
2019-01-22 12:41 ` [Qemu-devel] [PATCH] usb-mtp: replace the homebrew write with qemu_write_full Bandan Das
2019-01-24 8:01 ` Gerd Hoffmann
2019-01-24 8:19 ` Bandan Das [this message]
2019-01-24 8:31 ` Gerd Hoffmann
2019-04-24 6:07 ` [Qemu-devel] [Bug 1798780] Re: hw/usb/dev-mtp.c:1616: bad test ? Thomas Huth
2019-04-24 6:07 ` Thomas Huth
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=jpg4l9yzcw8.fsf@linux.bootlegged.copy \
--to=bsd@redhat.com \
--cc=1798780@bugs.launchpad.net \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.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).