From: Peter Maydell <peter.maydell@linaro.org>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: Does QEMU's coverity-scan run need to track coverity issues in dtb or slirp ?
Date: Mon, 2 Nov 2020 22:23:26 +0000 [thread overview]
Message-ID: <CAFEAcA8dfDPe2=iaMB3SVtJ3Z3ZPaqXVmxtQC2JYZ3AX2h_Uqw@mail.gmail.com> (raw)
In-Reply-To: <20201102203723.t7p4ildto3xbbdsx@function>
On Mon, 2 Nov 2020 at 20:37, Samuel Thibault <samuel.thibault@gnu.org> wrote:
>
> Hello,
>
> Peter Maydell, le lun. 02 nov. 2020 19:54:14 +0000, a ecrit:
> > Do dtc and slirp as upstream projects already track Coverity issues
>
> We started tracking them yes.
OK, so I can just dismiss anything that comes up in slirp/ in QEMU's
scan; that will help to cut down on the recent buildup.
thanks
-- PMM
next prev parent reply other threads:[~2020-11-02 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 19:54 Does QEMU's coverity-scan run need to track coverity issues in dtb or slirp ? Peter Maydell
2020-11-02 20:37 ` Samuel Thibault
2020-11-02 22:23 ` Peter Maydell [this message]
2020-11-03 1:41 ` David Gibson
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='CAFEAcA8dfDPe2=iaMB3SVtJ3Z3ZPaqXVmxtQC2JYZ3AX2h_Uqw@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@gnu.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).