From: Marcelo Schmitt <marcelo.schmitt1@gmail.com> To: corbet@lwn.net, mchehab+huawei@kernel.org, dlatypov@google.com, davidgow@google.com Cc: linux-doc@vger.kernel.org, linux-sparse@vger.kernel.org, cocci@inria.fr, smatch@vger.kernel.org, linux-kernel@vger.kernel.org, skhan@linuxfoundation.org, dan.carpenter@oracle.com, julia.lawall@inria.fr Subject: [PATCH v3 0/2] Add a section for static analysis tools Date: Wed, 30 Mar 2022 18:49:02 -0300 [thread overview] Message-ID: <cover.1648674305.git.marcelo.schmitt1@gmail.com> (raw) Hi all, This is the third patch version in the direction of complementing the testing guide documentation page with information about static analysis tools. Thank you for your suggestions and comments so far. These docs wouldn't get so helpful without them. Change log v2 -> v3: - Changed the paragraph about Sparse to make it sound better (hopefully) - Minor adjusts to make the considerations about Coccinelle sound better and be precise Change log v1 -> v2: - New patch adding considerations on when to use each tool - Brought generic tool characteristics to the intro paragraph - Made explicit that these tools run at compile time - Added a note of caution about false positives - Updated Coccinelle info to make it sound better and be more skimmable Marcelo Schmitt (2): Documentation: dev-tools: Add a section for static analysis tools Documentation: dev-tools: Enhance static analysis section with discussion Documentation/dev-tools/testing-overview.rst | 63 ++++++++++++++++++++ 1 file changed, 63 insertions(+) -- 2.35.1
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Schmitt <marcelo.schmitt1@gmail.com> To: corbet@lwn.net, mchehab+huawei@kernel.org, dlatypov@google.com, davidgow@google.com Cc: linux-doc@vger.kernel.org, linux-sparse@vger.kernel.org, cocci@inria.fr, smatch@vger.kernel.org, linux-kernel@vger.kernel.org, skhan@linuxfoundation.org, dan.carpenter@oracle.com, julia.lawall@inria.fr Subject: [cocci] [PATCH v3 0/2] Add a section for static analysis tools Date: Wed, 30 Mar 2022 18:49:02 -0300 [thread overview] Message-ID: <cover.1648674305.git.marcelo.schmitt1@gmail.com> (raw) Hi all, This is the third patch version in the direction of complementing the testing guide documentation page with information about static analysis tools. Thank you for your suggestions and comments so far. These docs wouldn't get so helpful without them. Change log v2 -> v3: - Changed the paragraph about Sparse to make it sound better (hopefully) - Minor adjusts to make the considerations about Coccinelle sound better and be precise Change log v1 -> v2: - New patch adding considerations on when to use each tool - Brought generic tool characteristics to the intro paragraph - Made explicit that these tools run at compile time - Added a note of caution about false positives - Updated Coccinelle info to make it sound better and be more skimmable Marcelo Schmitt (2): Documentation: dev-tools: Add a section for static analysis tools Documentation: dev-tools: Enhance static analysis section with discussion Documentation/dev-tools/testing-overview.rst | 63 ++++++++++++++++++++ 1 file changed, 63 insertions(+) -- 2.35.1
next reply other threads:[~2022-03-30 21:49 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-30 21:49 Marcelo Schmitt [this message] 2022-03-30 21:49 ` [cocci] [PATCH v3 0/2] Add a section for static analysis tools Marcelo Schmitt 2022-03-30 21:49 ` [PATCH v3 1/2] Documentation: dev-tools: " Marcelo Schmitt 2022-03-30 21:49 ` [cocci] " Marcelo Schmitt 2022-03-31 4:14 ` Dongliang Mu 2022-03-31 4:14 ` [cocci] " Dongliang Mu 2022-03-31 12:10 ` Marcelo Schmitt 2022-03-31 12:10 ` [cocci] " Marcelo Schmitt 2022-04-05 15:50 ` Jonathan Corbet 2022-04-05 15:50 ` Jonathan Corbet 2022-03-30 21:49 ` [PATCH v3 2/2] Documentation: dev-tools: Enhance static analysis section with discussion Marcelo Schmitt 2022-03-30 21:49 ` [cocci] " Marcelo Schmitt 2022-04-01 0:22 ` David Gow 2022-04-01 0:22 ` [cocci] " David Gow 2022-03-31 2:09 ` [PATCH v3 0/2] Add a section for static analysis tools David Gow 2022-03-31 2:09 ` [cocci] " David Gow
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=cover.1648674305.git.marcelo.schmitt1@gmail.com \ --to=marcelo.schmitt1@gmail.com \ --cc=cocci@inria.fr \ --cc=corbet@lwn.net \ --cc=dan.carpenter@oracle.com \ --cc=davidgow@google.com \ --cc=dlatypov@google.com \ --cc=julia.lawall@inria.fr \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-sparse@vger.kernel.org \ --cc=mchehab+huawei@kernel.org \ --cc=skhan@linuxfoundation.org \ --cc=smatch@vger.kernel.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.