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

[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 already track Coverity issues
(in which case we can just close the issues in the QEMU tracker as
irrelevant, or do we need to investigate these and potentially
forward them into whatever upstream bug tracker is appropriate?

thanks
-- PMM