From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: [Qemu-devel] [PATCH v3 0/2] slirp: Add support for RFC2132 TFTP server name
Date: Fri, 14 Sep 2018 15:26:14 +0800 [thread overview]
Message-ID: <20180914072616.17771-1-famz@redhat.com> (raw)
Post separatedly from the OpenBSD series for some more focus since the rest are
already queued.
Fam Zheng (2):
slirp: Add sanity check for str option length
slirp: Implement RFC2132 TFTP server name
net/slirp.c | 21 +++++++++++++++++++--
qapi/net.json | 5 ++++-
qemu-options.hx | 7 ++++++-
slirp/bootp.c | 45 +++++++++++++++++++++++++++++++++++----------
slirp/bootp.h | 1 +
slirp/libslirp.h | 1 +
slirp/slirp.c | 2 ++
slirp/slirp.h | 1 +
8 files changed, 69 insertions(+), 14 deletions(-)
--
2.17.1
next reply other threads:[~2018-09-14 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 7:26 Fam Zheng [this message]
2018-09-14 7:26 ` [Qemu-devel] [PATCH v3 1/2] slirp: Add sanity check for str option length Fam Zheng
2018-10-21 19:22 ` Samuel Thibault
2018-09-14 7:26 ` [Qemu-devel] [PATCH v3 2/2] slirp: Implement RFC2132 TFTP server name Fam Zheng
2018-10-21 19:25 ` Samuel Thibault
2018-10-22 13:01 ` Fam Zheng
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=20180914072616.17771-1-famz@redhat.com \
--to=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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).