From: no-reply@patchew.org
To: ppandit@redhat.com
Cc: pjp@fedoraproject.org, jasowang@redhat.com,
qemu-devel@nongnu.org, pangpei.lq@antfin.com,
svens@stackframe.org, ezrakiez@gmail.com
Subject: Re: [PATCH v3 0/2] net: tulip: add checks to avoid OOB access
Date: Tue, 3 Mar 2020 02:54:16 -0800 (PST) [thread overview]
Message-ID: <158323285548.8962.11834233941470798990@abdcc9e1aa82> (raw)
In-Reply-To: <20200303104724.233375-1-ppandit@redhat.com>
Patchew URL: https://patchew.org/QEMU/20200303104724.233375-1-ppandit@redhat.com/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#! /bin/bash
export ARCH=x86_64
make docker-image-fedora V=1 NETWORK=1
time make docker-test-mingw@fedora J=14 NETWORK=1
=== TEST SCRIPT END ===
The full log is available at
http://patchew.org/logs/20200303104724.233375-1-ppandit@redhat.com/testing.docker-mingw@fedora/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
next prev parent reply other threads:[~2020-03-03 10:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 10:47 [PATCH v3 0/2] net: tulip: add checks to avoid OOB access P J P
2020-03-03 10:47 ` [PATCH v3 1/2] net: tulip: check frame size and r/w data length P J P
2020-03-03 10:47 ` [PATCH v3 2/2] net: tulip: add .can_recieve routine P J P
2020-03-06 13:08 ` Stefan Hajnoczi
2020-03-16 18:01 ` P J P
2020-03-17 5:50 ` Jason Wang
2020-03-17 10:49 ` P J P
2020-03-18 2:07 ` Jason Wang
2020-03-19 9:58 ` P J P
2020-03-03 10:54 ` [PATCH v3 0/2] net: tulip: add checks to avoid OOB access no-reply
2020-03-05 12:16 ` P J P
2020-03-03 10:54 ` no-reply [this message]
2020-03-03 10:54 ` no-reply
2020-03-03 10:56 ` no-reply
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=158323285548.8962.11834233941470798990@abdcc9e1aa82 \
--to=no-reply@patchew.org \
--cc=ezrakiez@gmail.com \
--cc=jasowang@redhat.com \
--cc=pangpei.lq@antfin.com \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=svens@stackframe.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.