From: Paolo Bonzini <pbonzini@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>,
Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, philmd@linaro.org, david@redhat.com,
peterx@redhat.com, armbru@redhat.com,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] coverity: physmem: use simple assertions instead of modelling
Date: Wed, 15 Mar 2023 22:22:54 +0100 [thread overview]
Message-ID: <65a4bc93-ba15-7e60-765a-8691ebba94e5@redhat.com> (raw)
In-Reply-To: <fea4486a-cb0f-3a23-eb5b-56fa4a6bca77@yandex-team.ru>
On 3/15/23 15:28, Vladimir Sementsov-Ogievskiy wrote:
> On 22.02.23 18:57, Peter Maydell wrote:
>> On Wed, 22 Feb 2023 at 14:19, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>>>
>>> On Wed, 15 Feb 2023 at 15:22, Vladimir Sementsov-Ogievskiy
>>> <vsementsov@yandex-team.ru> wrote:
>>>>
>>>> ping
>>>>
>>>> [add Stefan]
>>>
>>> I'm not familiar with the Coverity models. Peter Maydell is the
>>> maintainer.
>>
>> We haven't run Coverity scans since September last year.
>
> What's the problem with it? May I help somehow?
The container broke when libslirp was removed, and I've been
procrastinating fixing it. :(
Paolo
>
>> There's no point making changes to our model until we've
>> fixed that. Paolo?
>>
>> thanks
>> -- PMM
>
next prev parent reply other threads:[~2023-03-15 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 22:03 [PATCH] coverity: physmem: use simple assertions instead of modelling Vladimir Sementsov-Ogievskiy
2023-01-09 13:37 ` Vladimir Sementsov-Ogievskiy
2023-01-23 11:05 ` David Hildenbrand
2023-02-15 20:20 ` Vladimir Sementsov-Ogievskiy
2023-02-22 14:18 ` Stefan Hajnoczi
2023-02-22 15:57 ` Peter Maydell
2023-03-15 14:28 ` Vladimir Sementsov-Ogievskiy
2023-03-15 21:22 ` Paolo Bonzini [this message]
2023-04-20 19:06 ` Vladimir Sementsov-Ogievskiy
2023-06-09 13:25 ` Vladimir Sementsov-Ogievskiy
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=65a4bc93-ba15-7e60-765a-8691ebba94e5@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=david@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
--cc=vsementsov@yandex-team.ru \
/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).