From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/1] Coverity model patches for 2018-07-05
Date: Thu, 5 Jul 2018 15:14:16 +0200 [thread overview]
Message-ID: <20180705131417.1847-1-armbru@redhat.com> (raw)
The following changes since commit 4fd1cbaf146d4ab35f465bba0fe23115c33cd5a7:
Merge remote-tracking branch 'remotes/armbru/tags/pull-monitor-2018-07-03-v2' into staging (2018-07-05 11:25:14 +0100)
are available in the Git repository at:
git://repo.or.cz/qemu/armbru.git tags/pull-cov-model-2018-07-05
for you to fetch changes up to 19020d41759c7d34eae78d6afbec27c523d55bcd:
coverity-model: Fix replay_get_byte() (2018-07-05 15:09:52 +0200)
----------------------------------------------------------------
Coverity model patches for 2018-07-05
----------------------------------------------------------------
Markus Armbruster (1):
coverity-model: Fix replay_get_byte()
scripts/coverity-model.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
--
2.17.1
next reply other threads:[~2018-07-05 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 13:14 Markus Armbruster [this message]
2018-07-05 13:14 ` [Qemu-devel] [PULL 1/1] coverity-model: Fix replay_get_byte() Markus Armbruster
2018-07-05 17:24 ` [Qemu-devel] [PULL 0/1] Coverity model patches for 2018-07-05 Peter Maydell
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=20180705131417.1847-1-armbru@redhat.com \
--to=armbru@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 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).