From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH] scripts/coverity-scan: Add xtensa and openrisc components
Date: Fri, 5 May 2023 10:21:48 +0200 [thread overview]
Message-ID: <e69b4e20-5ac2-bce9-fca4-86b566f975f7@redhat.com> (raw)
In-Reply-To: <20230504134526.2748157-1-peter.maydell@linaro.org>
On 5/4/23 15:45, Peter Maydell wrote:
> We have two target architectures which don't have Coverity components
> defined for them: xtensa and openrisc. Add them.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> As usual with coverity components, these will need to be added
> manually via the scanner UI, since it has no import-from-file...
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
but the UI is broken and adding the components results in a 404 for
https://scan.coverity.com/projects/qemu/update_components. :(
This has been a recurring issue through the years, it was gone about a
month ago and it's now back; I've sent an email to
scan-admin@coverity.com but I wouldn't hold my breath.
Paolo
> scripts/coverity-scan/COMPONENTS.md | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/scripts/coverity-scan/COMPONENTS.md b/scripts/coverity-scan/COMPONENTS.md
> index 7c48e0f1d21..add7c5a279c 100644
> --- a/scripts/coverity-scan/COMPONENTS.md
> +++ b/scripts/coverity-scan/COMPONENTS.md
> @@ -143,3 +143,9 @@ loongarch
>
> riscv
> ~ (/qemu)?((/include)?/hw/riscv/.*|/target/riscv/.*|/hw/.*/(riscv_|ibex_|sifive_).*)
> +
> +openrisc
> + ~ (/qemu)?((/include)?/hw/openrisc/.*|/target/openrisc/.*)
> +
> +xtensa
> + ~ (/qemu)?((/include)?/hw/xtensa/.*|/target/xtensa/.*)
prev parent reply other threads:[~2023-05-05 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 13:45 [PATCH] scripts/coverity-scan: Add xtensa and openrisc components Peter Maydell
2023-05-05 6:03 ` Stafford Horne
2023-05-05 8:21 ` Paolo Bonzini [this message]
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=e69b4e20-5ac2-bce9-fca4-86b566f975f7@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).