mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Norbert Manthey <nmanthey@amazon.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "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>,
	Kees Cook <keescook@chromium.org>, Kroah-Hartman <greg@kroah.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Coverity Scan model file, license, public access
Date: Tue, 6 Jul 2021 09:45:47 +0200	[thread overview]
Message-ID: <d7f096ee-7a9b-684e-433a-f8f3f0e6288d@amazon.de> (raw)

Dear all,

I would like to work with code analysis on the Linux kernel. The
currently used Coverity setup already uses a model file [1] to improve
the precision of the analysis. To the best of my knowledge, this model
file is currently not publicly accessible. I did not find a license
attached to  [1], nor any information about licensing.

To improve the way Coverity is used, I would like to move this model
file into a public repository, and add a license. I wonder whom else I
should involve into this process. Is there a recommended place for the
location of the license? I assume the targeted license should be GPL,
and would like to understand whether that works with the way this file
is currently maintained.

Best,
Norbert

[1] https://scan.coverity.com/projects/linux-next-weekly-scan/model_file




Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879



             reply	other threads:[~2021-07-06  7:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06  7:45 Norbert Manthey [this message]
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

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=d7f096ee-7a9b-684e-433a-f8f3f0e6288d@amazon.de \
    --to=nmanthey@amazon.de \
    --cc=dwmw@amazon.co.uk \
    --cc=foersleo@amazon.de \
    --cc=garsilva@embeddedor.com \
    --cc=greg@kroah.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®