From: Kroah-Hartman <greg@kroah.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: Kees Cook <keescook@chromium.org>,
Colin Ian King <colin.king@canonical.com>,
Dave Jones <davej@codemonkey.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
"foersleo@amazon.de" <foersleo@amazon.de>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
"Gustavo A. R. Silva" <garsilva@embeddedor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-hardening@vger.kernel.org,
Norbert Manthey <nmanthey@amazon.de>
Subject: Re: Coverity Scan model file, license, public access
Date: Sat, 18 Dec 2021 00:31:59 +0100 [thread overview]
Message-ID: <Yb0d70yFL4rCL1tq@kroah.com> (raw)
In-Reply-To: <1bce95f4-ddf8-2081-57c8-67cd9d4dd3d4@collabora.com>
On Sat, Dec 18, 2021 at 12:32:59AM +0500, Muhammad Usama Anjum wrote:
> > As far as I know, the model was written originally by Dave Jones, with
> > further changes from myself and, I think, Colin Ian King.
> >
> > I thought it was visible through the Coverity dashboard, once you're
> > logged in:
> > https://scan.coverity.com/projects/linux-next-weekly-scan?tab=analysis_settings
> > (See 'Modeling file loaded [View]')
> >
> I've sent the request to join the dashboard. Who is the maintainer of
> this free Coverity dashboard? Can anyone use these results to fix the
> bugs without the permission of anyone?
Yes, no permission needed, fix away!
prev parent reply other threads:[~2021-12-17 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 7:45 Coverity Scan model file, license, public access Norbert Manthey
2021-07-06 16:54 ` Kroah-Hartman
[not found] ` <6f1cb856-fc72-cfd1-9bdd-b4dbf58c558c@amazon.de>
2021-07-06 18:41 ` Kroah-Hartman
[not found] ` <b5f5c38c-5691-816d-f14c-8a82be7d9456@amazon.de>
2021-07-07 5:16 ` Kroah-Hartman
2021-07-15 13:12 ` Norbert Manthey
2021-07-15 18:25 ` Kees Cook
2021-07-16 10:26 ` Norbert Manthey
2021-12-17 19:32 ` Muhammad Usama Anjum
2021-12-17 20:03 ` Gustavo A. R. Silva
2021-12-17 23:31 ` Kroah-Hartman [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=Yb0d70yFL4rCL1tq@kroah.com \
--to=greg@kroah.com \
--cc=colin.king@canonical.com \
--cc=davej@codemonkey.org.uk \
--cc=dwmw@amazon.co.uk \
--cc=foersleo@amazon.de \
--cc=garsilva@embeddedor.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nmanthey@amazon.de \
--cc=tglx@linutronix.de \
--cc=usama.anjum@collabora.com \
/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