From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
patchew-devel@redhat.com
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Michael Rolnik" <mrolnik@gmail.com>,
"Sarah Harris" <S.E.Harris@kent.ac.uk>
Subject: Re: [PATCH v3 0/8] hw/avr: Introduce the Arduino boards
Date: Mon, 30 Dec 2019 00:18:40 +0100 [thread overview]
Message-ID: <CAAdtpL6pg7zCkrcb5kmZ=mxBucJOmah8cORFQf=tW8FOWMQW3w@mail.gmail.com> (raw)
In-Reply-To: <157766026188.19009.2772418918814016586@37313f22b938>
On Sun, Dec 29, 2019 at 11:58 PM <no-reply@patchew.org> wrote:
> This series failed the docker-quick@centos7 build test. Please find the testing commands and
> their output below. If you have Docker installed, you can probably reproduce it
> locally.
> Please send your feedback to patchew-devel@redhat.com
Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
From https://github.com/patchew-project/qemu
- [tag update] patchew/20191229215158.5788-1-mrolnik@gmail.com
-> patchew/20191229215158.5788-1-mrolnik@gmail.com
* [new tag] patchew/20191229224505.24466-1-f4bug@amsat.org ->
patchew/20191229224505.24466-1-f4bug@amsat.org
fatal: failed to write ref-pack file
fatal: The remote end hung up unexpectedly
Is patchew disk full?
next prev parent reply other threads:[~2019-12-29 23:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 22:44 [PATCH v3 0/8] hw/avr: Introduce the Arduino boards Philippe Mathieu-Daudé
2019-12-29 22:44 ` [PATCH v3 1/8] hw/char/avr: Reduce USART I/O size Philippe Mathieu-Daudé
2019-12-29 22:44 ` [PATCH v3 2/8] hw/timer/avr_timer16: Rename memory region debugging name Philippe Mathieu-Daudé
2019-12-29 22:45 ` [PATCH v3 3/8] hw/avr: Add some ATmega microcontrollers Philippe Mathieu-Daudé
2019-12-29 22:45 ` [PATCH v3 4/8] hw/avr: Add some Arduino boards Philippe Mathieu-Daudé
2020-01-20 9:03 ` Igor Mammedov
2020-01-20 9:21 ` Philippe Mathieu-Daudé
2020-01-20 10:09 ` Igor Mammedov
2020-01-20 11:05 ` Philippe Mathieu-Daudé
2020-01-20 14:48 ` Igor Mammedov
2019-12-29 22:45 ` [PATCH v3 5/8] tests/boot-serial-test: Test some Arduino boards (AVR based) Philippe Mathieu-Daudé
2019-12-29 22:45 ` [PATCH v3 6/8] tests/acceptance: Do not set the machine type manually Philippe Mathieu-Daudé
2019-12-30 14:10 ` Wainer dos Santos Moschetta
2019-12-29 22:45 ` [PATCH v3 7/8] tests/acceptance: Keep multilines comment consistent with other tests Philippe Mathieu-Daudé
2019-12-29 22:45 ` [PATCH v3 8/8] tests/acceptance: Test the Arduino MEGA2560 board Philippe Mathieu-Daudé
2019-12-29 22:57 ` [PATCH v3 0/8] hw/avr: Introduce the Arduino boards no-reply
2019-12-29 23:18 ` Philippe Mathieu-Daudé [this message]
2019-12-30 18:17 ` Michael Rolnik
2020-01-19 22:50 ` Philippe Mathieu-Daudé
2020-01-20 5:29 ` Michael Rolnik
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='CAAdtpL6pg7zCkrcb5kmZ=mxBucJOmah8cORFQf=tW8FOWMQW3w@mail.gmail.com' \
--to=f4bug@amsat.org \
--cc=S.E.Harris@kent.ac.uk \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mrolnik@gmail.com \
--cc=patchew-devel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).