From: Lars Kurth <lars.kurth@citrix.com>
To: Artem Mygaiev <artem_mygaiev@epam.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Julien Grall <julien.grall@arm.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Artem Mygaiev <joculator@gmail.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [COVERITY ACCESS] for Embedded/Automotive team
Date: Mon, 28 Nov 2016 10:27:03 +0000 [thread overview]
Message-ID: <D461B61C.309EF%lars.kurth@citrix.com> (raw)
In-Reply-To: <3fc1366f-6ab7-a14f-ea9f-761e82f85f5d@epam.com>
On 22/11/2016 13:54, "Artem Mygaiev" <artem_mygaiev@epam.com> wrote:
>On 22.11.16 15:42, Andrew Cooper wrote:
>>
>>
>> The only way we could scan for ARM is if we could be given multiple
>> different streams (one per arch) to use, and Coverity have already said
>> no to this request. This is a politics problem, not a technical
>>problem.
>
>Andrew, I understand, thanks.
Andrew, thanks for the clarification.
>Would it be still possible to get Scan model files for us? We would like
>to update them for use with ARM. BTW, we could set up ARM build Coverity
>Scan with GitHub/Travis only limited by amount of runs per week
>(depending on number LOC number).
Artem, just to clarify.
I am assuming you have a license for Coverity that would allow you to run
it on a different configuration: Correct?
And there are some constraints on how frequently this could be run?
And you would be willing to run this on behalf of the project for an ARM
configuration?
Regards
Lars
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-28 10:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 13:36 [COVERITY ACCESS] for Embedded/Automotive team Artem Mygaiev
2016-11-18 13:56 ` Andrew Cooper
2016-11-18 15:28 ` Konrad Rzeszutek Wilk
2016-11-18 20:55 ` Julien Grall
2016-11-19 16:53 ` Lars Kurth
2016-11-22 11:51 ` Julien Grall
2016-11-22 11:55 ` Lars Kurth
2016-11-22 13:06 ` Artem Mygaiev
2016-11-22 13:42 ` Andrew Cooper
2016-11-22 13:54 ` Artem Mygaiev
2016-11-28 10:27 ` Lars Kurth [this message]
2016-11-28 11:01 ` Artem Mygaiev
2016-11-29 14:21 ` Artem Mygaiev
2016-11-29 14:27 ` Julien Grall
2016-11-29 15:04 ` Lars Kurth
2016-11-30 11:14 ` Artem Mygaiev
2016-11-29 15:09 ` Artem Mygaiev
2016-11-29 16:12 ` Julien Grall
2016-11-29 18:19 ` Stefano Stabellini
2016-11-30 11:15 ` Artem Mygaiev
2016-11-30 19:10 ` Stefano Stabellini
2016-11-30 19:21 ` Andrew Cooper
2016-12-01 13:44 ` Artem Mygaiev
2016-11-22 9:00 ` Artem Mygaiev
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=D461B61C.309EF%lars.kurth@citrix.com \
--to=lars.kurth@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=artem_mygaiev@epam.com \
--cc=joculator@gmail.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).