Re: Does QEMU's coverity-scan run need to track coverity issues in dtb or slirp ?

2020-11-02 Thread David Gibson
On Mon, Nov 02, 2020 at 07:54:14PM +, Peter Maydell wrote: > Currently QEMU's Coverity-Scan project has a bunch of unresolved > issues in code in dtc/ and also in slirp/. (I suspect most of them > are actually false-positives that got re-reported when we switched > to Meson and the filenames

Re: Does QEMU's coverity-scan run need to track coverity issues in dtb or slirp ?

2020-11-02 Thread Peter Maydell
On Mon, 2 Nov 2020 at 20:37, Samuel Thibault wrote: > > Hello, > > Peter Maydell, le lun. 02 nov. 2020 19:54:14 +, 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

Re: Does QEMU's coverity-scan run need to track coverity issues in dtb or slirp ?

2020-11-02 Thread Samuel Thibault
Hello, Peter Maydell, le lun. 02 nov. 2020 19:54:14 +, a ecrit: > Do dtc and slirp as upstream projects already track Coverity issues We started tracking them yes. Samuel

Does QEMU's coverity-scan run need to track coverity issues in dtb or slirp ?

2020-11-02 Thread Peter Maydell
Currently QEMU's Coverity-Scan project has a bunch of unresolved issues in code in dtc/ and also in slirp/. (I suspect most of them are actually false-positives that got re-reported when we switched to Meson and the filenames changed, or some similar event.) Do dtc and slirp as upstream projects