From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] coverity: put NUBus under m68k component
Date: Mon, 5 Sep 2022 13:54:20 +0100 [thread overview]
Message-ID: <CAFEAcA_UK6ZxkFXh2_P_qBdYptYFNqMPaGV_AMF1orcip4zzKQ@mail.gmail.com> (raw)
In-Reply-To: <20220905102633.20940-1-pbonzini@redhat.com>
On Mon, 5 Sept 2022 at 12:07, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> It is only used by the Q800 emulation, so put it under that architecture.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> scripts/coverity-scan/COMPONENTS.md | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/coverity-scan/COMPONENTS.md b/scripts/coverity-scan/COMPONENTS.md
> index fc1608932e..0e6ab4936e 100644
> --- a/scripts/coverity-scan/COMPONENTS.md
> +++ b/scripts/coverity-scan/COMPONENTS.md
> @@ -22,7 +22,7 @@ i386
> ~ (/qemu)?((/include)?/hw/i386/.*|/target/i386/.*|/hw/intc/[^/]*apic[^/]*\.c)
>
> m68k
> - ~ (/qemu)?((/include)?/hw/m68k/.*|/target/m68k/.*|(/include)?/hw(/.*)?/mcf.*)
> + ~ (/qemu)?((/include)?/hw/m68k/.*|/target/m68k/.*|(/include)?/hw(/.*)?/mcf.*|(/include)?/hw/nubus/.*)
>
> microblaze
> ~ (/qemu)?((/include)?/hw/microblaze/.*|/target/microblaze/.*)
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
On the subject of coverity components:
* we should drop the 'capstone' component now we've removed that submodule
* https://scan.coverity.com/projects/qemu?tab=overview says the 'hvf'
component has 0 lines in it, which suggests we got that regex wrong
somehow, or there's an ordering issue and some higher-up component
has already claimed all the files
thanks
-- PMM
next prev parent reply other threads:[~2022-09-05 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 10:26 [PATCH] coverity: put NUBus under m68k component Paolo Bonzini
2022-09-05 12:54 ` Peter Maydell [this message]
2022-09-05 14:16 ` Philippe Mathieu-Daudé via
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=CAFEAcA_UK6ZxkFXh2_P_qBdYptYFNqMPaGV_AMF1orcip4zzKQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=pbonzini@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).