From: Samuel Thibault <samuel.thibault@gnu.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "J. Kiszka" <jan.kiszka@siemens.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL] slirp: Fix memory leak on small incoming ipv4 packet
Date: Tue, 22 Mar 2016 00:49:07 +0100 [thread overview]
Message-ID: <20160321234907.GS4946@var.home> (raw)
In-Reply-To: <CAFEAcA9uZ4Z9ajrwKhFZaN+7NYF_iLezzGw+hNXWYfvWLX-i9Q@mail.gmail.com>
Hello,
Peter Maydell, on Mon 21 Mar 2016 09:48:48 +0000, wrote:
> Generally the
> process for QEMU is that first patches are sent as normal [PATCH] mails,
> for code review. Patches should only be put into pull requests once
> they've been through the review process. (And then you can batch them
> up so you don't have to send me two pulls for one patch each.)
Ah OK. Since they were one-liners, I thought they didn't need the review
step. Now resent for review.
Samuel
next prev parent reply other threads:[~2016-03-21 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 14:05 [Qemu-devel] [PULL] slirp: Fix memory leak on small incoming ipv4 packet Samuel Thibault
2016-03-20 14:05 ` Samuel Thibault
2016-03-21 9:48 ` Peter Maydell
2016-03-21 23:49 ` Samuel Thibault [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-20 11:23 Samuel Thibault
2016-03-20 14:06 ` Samuel Thibault
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=20160321234907.GS4946@var.home \
--to=samuel.thibault@gnu.org \
--cc=jan.kiszka@siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.