mbox

[PULL] slirp: Fix memory leak on small incoming ipv4 packet

Message ID 1458482736-7075-1-git-send-email-samuel.thibault@ens-lyon.org
State New
Headers show

Pull-request

http://people.debian.org/~sthibault/qemu.git tags/samuel-thibault

Message

Samuel Thibault March 20, 2016, 2:05 p.m. UTC
The following changes since commit 4829e0378dfb91d55af9dfd741bd09e8f2c4f91a:

  Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2016-03-18' into staging (2016-03-18 17:18:41 +0000)

are available in the git repository at:

  http://people.debian.org/~sthibault/qemu.git tags/samuel-thibault

for you to fetch changes up to 6f843b773c2fdec99f1d27081b0cc80fede76493:

  slirp: Fix memory leak on small incoming ipv4 packet (2016-03-20 12:17:16 +0100)

----------------------------------------------------------------
slirp: Fix memory leak on small incoming ipv4 packet

----------------------------------------------------------------
Samuel Thibault (1):
      slirp: Fix memory leak on small incoming ipv4 packet

 slirp/ip_input.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

Peter Maydell March 21, 2016, 9:48 a.m. UTC | #1
On 20 March 2016 at 14:05, Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
> The following changes since commit 4829e0378dfb91d55af9dfd741bd09e8f2c4f91a:
>
>   Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2016-03-18' into staging (2016-03-18 17:18:41 +0000)
>
> are available in the git repository at:
>
>   http://people.debian.org/~sthibault/qemu.git tags/samuel-thibault
>
> for you to fetch changes up to 6f843b773c2fdec99f1d27081b0cc80fede76493:
>
>   slirp: Fix memory leak on small incoming ipv4 packet (2016-03-20 12:17:16 +0100)
>
> ----------------------------------------------------------------
> slirp: Fix memory leak on small incoming ipv4 packet
>
> ----------------------------------------------------------------
> Samuel Thibault (1):
>       slirp: Fix memory leak on small incoming ipv4 packet

Hi -- I couldn't find where these patches had been sent to the mailing
list previously (though it's possible I missed them). 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.)

thanks
-- PMM
Samuel Thibault March 21, 2016, 11:49 p.m. UTC | #2
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