From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: qemu-devel@nongnu.org,
Cc: antoine.damhet@blade-group.com, pbonzini@redhat.com,
mtosatti@redhat.com, ehabkost@redhat.com, dgilbert@redhat.com
Subject: Re: [PATCH] target/i386: always create kvmclock device
Date: Thu, 17 Sep 2020 13:41:30 +0200 [thread overview]
Message-ID: <87imcchbpx.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <160034151689.8478.18235018336121752129@66eaa9a8a123>
no-reply@patchew.org writes:
> Patchew URL: https://patchew.org/QEMU/20200917111306.819263-1-vkuznets@redhat.com/
>
>
>
> Hi,
>
> This series seems to have some coding style problems. See output below for
> more information:
>
> N/A. Internal error while reading log file
error: copy-fd: write returned No space left on device
fatal: failed to copy file to '/var/tmp/patchew-tester-tmp-h4pn40by/src/.git/objects/pack/pack-614a2d933aa3d31ccd9f7bddf2f28bf8fae5e07c.pack': No space left on device
fatal: The remote end hung up unexpectedly
does not look like something I can fix. No idea why 'no space left' is
called a 'coding style problem' btw :-)
--
Vitaly
next prev parent reply other threads:[~2020-09-17 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 11:13 [PATCH] target/i386: always create kvmclock device Vitaly Kuznetsov
2020-09-17 11:18 ` no-reply
2020-09-17 11:41 ` Vitaly Kuznetsov [this message]
2020-09-17 12:25 ` Antoine Damhet
2020-09-17 13:34 ` Vitaly Kuznetsov
2020-09-17 14:42 ` Dr. David Alan Gilbert
2020-09-17 14:58 ` Vitaly Kuznetsov
2020-09-17 17:44 ` Dr. David Alan Gilbert
2020-09-18 8:39 ` Paolo Bonzini
2020-09-18 15:12 ` Antoine Damhet
2020-09-18 15:26 ` Dr. David Alan Gilbert
2020-09-22 15:19 ` Vitaly Kuznetsov
2020-09-17 15:00 ` Antoine Damhet
2020-09-18 8:38 ` Paolo Bonzini
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=87imcchbpx.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=antoine.damhet@blade-group.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--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.