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 v2 0/2] Add a section for static analysis tools Date: Tue, 29 Mar 2022 20:21:48 -0300 [thread overview] Message-ID: <cover.1648593132.git.marcelo.schmitt1@gmail.com> (raw) Hi, Thanks to everybody who commented on v1 for your kind and much helpful feedback. I tried to add suggestions and ideas while keeping the text concise. Also, I took Dan and Julia's comments and included them into the documentation (patch 2) because I think they were very helpful in comparing the tools. I didn't feel comfortable adding something comparing Sparse and Coccinelle directly as I'm not an expert with any of these tools either. Anyhow, that can be something to do in the future. Thanks, Marcelo 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 | 64 ++++++++++++++++++++ 1 file changed, 64 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 v2 0/2] Add a section for static analysis tools Date: Tue, 29 Mar 2022 20:21:48 -0300 [thread overview] Message-ID: <cover.1648593132.git.marcelo.schmitt1@gmail.com> (raw) Hi, Thanks to everybody who commented on v1 for your kind and much helpful feedback. I tried to add suggestions and ideas while keeping the text concise. Also, I took Dan and Julia's comments and included them into the documentation (patch 2) because I think they were very helpful in comparing the tools. I didn't feel comfortable adding something comparing Sparse and Coccinelle directly as I'm not an expert with any of these tools either. Anyhow, that can be something to do in the future. Thanks, Marcelo 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 | 64 ++++++++++++++++++++ 1 file changed, 64 insertions(+) -- 2.35.1
next reply other threads:[~2022-03-29 23:22 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-29 23:21 Marcelo Schmitt [this message] 2022-03-29 23:21 ` [cocci] [PATCH v2 0/2] Add a section for static analysis tools Marcelo Schmitt 2022-03-29 23:22 ` [PATCH v2 1/2] Documentation: dev-tools: " Marcelo Schmitt 2022-03-29 23:22 ` [cocci] " Marcelo Schmitt 2022-03-29 23:48 ` Daniel Latypov 2022-03-29 23:48 ` [cocci] " Daniel Latypov 2022-03-30 2:33 ` David Gow 2022-03-30 2:33 ` [cocci] " David Gow 2022-03-30 8:04 ` Julia Lawall 2022-03-30 8:04 ` [cocci] " Julia Lawall 2022-03-29 23:23 ` [PATCH v2 2/2] Documentation: dev-tools: Enhance static analysis section with discussion Marcelo Schmitt 2022-03-29 23:23 ` [cocci] " Marcelo Schmitt 2022-03-30 2:48 ` David Gow 2022-03-30 2:48 ` [cocci] " David Gow 2022-03-30 8:07 ` Julia Lawall 2022-03-30 8:07 ` [cocci] " Julia Lawall 2022-03-30 19:30 ` Marcelo Schmitt 2022-03-30 19:30 ` [cocci] " Marcelo Schmitt 2022-04-01 0:18 ` David Gow 2022-04-01 0:18 ` [cocci] " David Gow 2022-03-31 8:14 ` Dan Carpenter 2022-03-31 8:14 ` [cocci] " Dan Carpenter 2022-04-01 0:19 ` David Gow 2022-04-01 0:19 ` [cocci] " David Gow 2022-03-30 8:06 ` Julia Lawall 2022-03-30 8:06 ` [cocci] " Julia Lawall
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.1648593132.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.