From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH 4/4] slirp: clean up slirp_update_timeout
Date: Tue, 17 Sep 2013 12:50:25 +0200 [thread overview]
Message-ID: <426e3e6ce1abdb0d85faefbfac3cf4dcc7f224a3.1379415024.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1379415024.git.jan.kiszka@siemens.com>
In-Reply-To: <cover.1379415024.git.jan.kiszka@siemens.com>
No need to write out the timeout early, keep it local until we are done.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
slirp/slirp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/slirp/slirp.c b/slirp/slirp.c
index fe16367..bad8dad 100644
--- a/slirp/slirp.c
+++ b/slirp/slirp.c
@@ -270,8 +270,8 @@ static void slirp_update_timeout(uint32_t *timeout)
if (*timeout <= TIMEOUT_FAST) {
return;
}
- *timeout = MIN(1000, *timeout);
- t = *timeout;
+
+ t = MIN(1000, *timeout);
/* If we have tcp timeout with slirp, then we will fill @timeout with
* more precise value.
--
1.8.1.1.298.ge7eed54
next prev parent reply other threads:[~2013-09-17 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 10:50 [Qemu-devel] [PATCH 0/4] [PULL] slirp: improve timeout management Jan Kiszka
2013-09-17 10:50 ` [Qemu-devel] [PATCH 1/4] slirp: make timeout local Jan Kiszka
2013-09-17 10:50 ` [Qemu-devel] [PATCH 2/4] slirp: define timeout as macro Jan Kiszka
2013-09-17 10:50 ` [Qemu-devel] [PATCH 3/4] slirp: set mainloop timeout with more precise value Jan Kiszka
2013-09-17 10:50 ` Jan Kiszka [this message]
2013-09-17 10:53 ` [Qemu-devel] [PATCH 0/4] [PULL] slirp: improve timeout management Jan Kiszka
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=426e3e6ce1abdb0d85faefbfac3cf4dcc7f224a3.1379415024.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@us.ibm.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).