From: Jonathan Corbet <corbet@lwn.net>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>,
Dongliang Mu <mudongliangabcd@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
dlatypov@google.com, davidgow@google.com,
linux-doc@vger.kernel.org, linux-sparse@vger.kernel.org,
cocci@inria.fr, smatch@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
skhan@linuxfoundation.org,
Dan Carpenter <dan.carpenter@oracle.com>,
julia.lawall@inria.fr
Subject: Re: [PATCH v3 1/2] Documentation: dev-tools: Add a section for static analysis tools
Date: Tue, 05 Apr 2022 09:50:19 -0600 [thread overview]
Message-ID: <87y20jedhg.fsf@meer.lwn.net> (raw)
In-Reply-To: <YkWaL26K7UjKB0sa@marsc.168.1.7>
Marcelo Schmitt <marcelo.schmitt1@gmail.com> writes:
> On 03/31, Dongliang Mu wrote:
>> Should we include static analysis tools based on LLVM? For example,
>> Clang static analysis.
>
> I think that would be a good addition. I haven't checked out Clang tools
> though, so it would take me a bit more time to write something about that.
That seems like a good topic for a future patch. Meanwhile I've applied
this series, thanks.
jon
next prev parent reply other threads:[~2022-04-05 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 21:49 [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-31 4:14 ` Dongliang Mu
2022-03-31 12:10 ` Marcelo Schmitt
2022-04-05 15:50 ` Jonathan Corbet [this message]
2022-03-30 21:49 ` [PATCH v3 2/2] Documentation: dev-tools: Enhance static analysis section with discussion Marcelo Schmitt
2022-04-01 0:22 ` David Gow
2022-03-31 2:09 ` [PATCH v3 0/2] Add a section for static analysis tools 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=87y20jedhg.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=cocci@inria.fr \
--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=marcelo.schmitt1@gmail.com \
--cc=mchehab+huawei@kernel.org \
--cc=mudongliangabcd@gmail.com \
--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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).