From: Thomas Horsten <thomas@horsten.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [tftp] Handle TFTP ERROR from client
Date: Tue, 12 Jan 2010 22:38:44 +0000 [thread overview]
Message-ID: <5d932cdc1001121438k38c8c98fp9d60cd1e5660423a@mail.gmail.com> (raw)
In-Reply-To: <4B4B80DE.4050607@codemonkey.ws>
2010/1/11 Anthony Liguori <anthony@codemonkey.ws>:
> On 01/07/2010 11:01 AM, Thomas Horsten wrote:
>> ...The patch from Milan Plzik to return
>> after sending OACK is also required for a complete fix.
> Applied. Thanks.
Thanks. It appears that the patch Milan submitted was missed (probably
because it was in a response to a thread), could you please apply that
one as well?
The subject was "Qemu's internal TFTP server breaks lock-step-iness of
TFTP", and it's archived here:
http://lists.gnu.org/archive/html/qemu-devel/2010-01/msg00449.html
Thomas
next prev parent reply other threads:[~2010-01-12 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 17:01 [Qemu-devel] [PATCH] [tftp] Handle TFTP ERROR from client Thomas Horsten
2010-01-11 19:49 ` Anthony Liguori
2010-01-12 22:38 ` Thomas Horsten [this message]
2010-01-12 22:57 ` Anthony Liguori
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=5d932cdc1001121438k38c8c98fp9d60cd1e5660423a@mail.gmail.com \
--to=thomas@horsten.com \
--cc=anthony@codemonkey.ws \
--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).