From: Samuel Thibault <samuel.thibault@gnu.org>
To: "Hervé Poussineau" <hpoussin@reactos.org>
Cc: qemu-devel@nongnu.org, hpa@zytor.com,
Stefan Hajnoczi <stefanha@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] [PATCH] slirp: support dynamic block size for TFTP transfers
Date: Wed, 21 Dec 2016 00:03:57 +0100 [thread overview]
Message-ID: <20161220230357.GQ3258@var.home> (raw)
In-Reply-To: <1479757549-18672-1-git-send-email-hpoussin@reactos.org>
Hervé Poussineau, on Mon 21 Nov 2016 20:45:49 +0100, wrote:
> The blocksize option is defined in RFC 1783.
> We now support block sizes between 1 and 1432 bytes, instead of 512 only.
>
> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
I fixed a couple of trivial things and commited to my tree, thanks!
Samuel
prev parent reply other threads:[~2016-12-20 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 19:45 [Qemu-devel] [PATCH] slirp: support dynamic block size for TFTP transfers Hervé Poussineau
2016-11-21 19:49 ` no-reply
2016-11-21 19:51 ` H. Peter Anvin
2016-11-22 8:19 ` Thomas Huth
2016-12-20 23:03 ` Samuel Thibault [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=20161220230357.GQ3258@var.home \
--to=samuel.thibault@gnu.org \
--cc=hpa@zytor.com \
--cc=hpoussin@reactos.org \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).