From: Markus Armbruster <armbru@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH v4 0/2] error-report: introduce {error|warn}_report_once
Date: Wed, 15 Aug 2018 07:58:52 +0200 [thread overview]
Message-ID: <87mutop3vn.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20180524044454.11792-1-peterx@redhat.com> (Peter Xu's message of "Thu, 24 May 2018 12:44:52 +0800")
I'm afraid I let this fall through the cracks. Sorry about that!
PATCH 2 conflicts semantically with commmit 63b88968f13: the latter adds
a trace_vtd_err() the former doesn't replace. Please respin.
next prev parent reply other threads:[~2018-08-15 5:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 4:44 [Qemu-devel] [PATCH v4 0/2] error-report: introduce {error|warn}_report_once Peter Xu
2018-05-24 4:44 ` [Qemu-devel] [PATCH v4 1/2] qemu-error: " Peter Xu
2018-05-29 9:30 ` Cornelia Huck
2018-05-30 3:30 ` Peter Xu
2018-05-30 13:36 ` Cornelia Huck
2018-06-13 7:56 ` Markus Armbruster
2018-05-30 4:47 ` Michael S. Tsirkin
2018-05-30 6:39 ` Peter Xu
2018-05-30 13:53 ` Cornelia Huck
2018-06-13 7:59 ` Markus Armbruster
2018-05-30 15:15 ` Halil Pasic
2018-05-30 15:19 ` Michael S. Tsirkin
2018-05-30 15:30 ` Halil Pasic
2018-06-13 8:01 ` Markus Armbruster
2018-06-13 9:08 ` Peter Xu
2018-05-24 4:44 ` [Qemu-devel] [PATCH v4 2/2] intel-iommu: start to use error_report_once Peter Xu
2018-06-13 8:05 ` Markus Armbruster
2018-06-13 9:36 ` Auger Eric
2018-06-14 12:51 ` Markus Armbruster
2018-06-14 12:56 ` Peter Maydell
2018-08-15 5:58 ` Markus Armbruster [this message]
2018-08-15 6:10 ` [Qemu-devel] [PATCH v4 0/2] error-report: introduce {error|warn}_report_once Peter Xu
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=87mutop3vn.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=f4bug@amsat.org \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@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.