From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v2 0/2] Libclang based analyzer
Date: Fri, 4 Jun 2021 14:52:39 +0200 [thread overview]
Message-ID: <YLoiF6Wy6cALM0Yy@yuki> (raw)
In-Reply-To: <20210604111434.21422-1-rpalethorpe@suse.com>
Hi!
> Compared to the Coccinelle version it's very ugly. However I think
> this will allow us to get all the low hanging fruit without creating
> major problems for test developers.
I had a look at the code and it does not seem to be that bad. It's
longer due to some boiler plate and more explicit but not necessarily
ugly.
> I guess it could be run during CI if we either fix all the existing
> TEST() usages in the library or add an ignore list. I already have a
> Coccinelle script to help with the former.
I will have a look at the patches generated by coccinelle, I supposed
that we want to merge them regardless.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2021-06-04 12:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 11:14 [LTP] [RFC PATCH v2 0/2] Libclang based analyzer Richard Palethorpe
2021-06-04 11:14 ` [LTP] [RFC PATCH v2 1/2] Add 'make check' and clang-check to build system Richard Palethorpe
2021-06-04 14:10 ` Petr Vorel
2021-06-04 14:11 ` Cyril Hrubis
2021-06-04 14:28 ` Richard Palethorpe
2021-06-04 14:33 ` Cyril Hrubis
2021-06-07 9:18 ` Joerg Vehlow
2021-06-07 9:12 ` Cyril Hrubis
2021-06-11 13:49 ` Petr Vorel
2021-06-11 14:17 ` Petr Vorel
2021-06-14 11:09 ` Richard Palethorpe
2021-06-04 11:14 ` [LTP] [RFC PATCH v2 2/2] Start libclang based analyzer and TEST() check Richard Palethorpe
2021-06-04 12:52 ` Cyril Hrubis [this message]
2021-06-04 13:50 ` [LTP] [RFC PATCH v2 0/2] Libclang based analyzer Richard Palethorpe
2021-06-07 8:37 ` Joerg Vehlow
2021-06-07 9:14 ` Cyril Hrubis
2021-06-07 10:20 ` Richard Palethorpe
2021-06-07 11:34 ` Joerg Vehlow
2021-06-07 13:42 ` Cyril Hrubis
2021-06-07 13:49 ` Richard Palethorpe
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=YLoiF6Wy6cALM0Yy@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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