From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 1/8] Add Sparse based checker and TST_RET/ERR check
Date: Wed, 14 Jul 2021 14:06:51 +0100 [thread overview]
Message-ID: <87y2a9nixg.fsf@suse.de> (raw)
In-Reply-To: <36430750-17c9-06e4-0f49-efc744116154@jv-coder.de>
Hello Joerg,
Joerg Vehlow <lkml@jv-coder.de> writes:
> Hi,
>
>
> On 7/14/2021 9:11 AM, Richard Palethorpe via ltp wrote:
>> Vendors in Sparse as a git module. Then uses it to check for stores to
>> TST_RET/ERR within the library.
>>
>> Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
>> ---
>> .gitmodules | 3 +
>> tools/Makefile | 2 +
>> tools/sparse/.gitignore | 1 +
>> tools/sparse/Makefile | 27 ++++++++
>> tools/sparse/README.md | 38 +++++++++++
>> tools/sparse/main.c | 148 ++++++++++++++++++++++++++++++++++++++++
> I think the name could be a bit better... sparse_main or ltp_checker
> or something, because a binary just called main could be confusing.
Sure or maybe sparse-ltp?
That would fit with upstream IMO.
>
> Otherwise good basis for additional checks and fixing the warnings
> emitted by sparse will allow use to raise the overall warning level.
> Hopefully at some point at least "-Wall -Werror" is possible.
>
> Joerg
Yes, I would really like to see -Wall enabled by default. Also Sparse
can maybe help highlight wierd crap only GCC and Clang accept.
--
Thank you,
Richard.
next prev parent reply other threads:[~2021-07-14 13:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 7:11 [LTP] [PATCH v2 0/8] Sparse based checker and rule proposal Richard Palethorpe
2021-07-14 7:11 ` [LTP] [PATCH v2 1/8] Add Sparse based checker and TST_RET/ERR check Richard Palethorpe
2021-07-14 10:43 ` Petr Vorel
2021-07-14 11:21 ` Joerg Vehlow
2021-07-14 13:06 ` Richard Palethorpe [this message]
2021-07-19 14:51 ` Cyril Hrubis
2021-07-14 7:11 ` [LTP] [PATCH v2 2/8] Add 'make check' to the build system Richard Palethorpe
2021-07-14 10:46 ` Petr Vorel
2021-07-14 7:11 ` [LTP] [PATCH v2 3/8] doc: Add rules and recommendations list Richard Palethorpe
2021-07-14 10:49 ` Petr Vorel
2021-07-14 13:15 ` Richard Palethorpe
2021-07-21 15:43 ` Petr Vorel
2021-07-14 10:54 ` Petr Vorel
2021-07-14 13:26 ` Richard Palethorpe
2021-07-14 14:34 ` Petr Vorel
2021-07-14 7:11 ` [LTP] [PATCH v2 4/8] doc: Remind authors and maintainers to run make check Richard Palethorpe
2021-07-14 10:56 ` Petr Vorel
2021-07-14 13:34 ` Richard Palethorpe
2021-07-14 14:30 ` Petr Vorel
2021-07-14 7:11 ` [LTP] [PATCH v2 5/8] doc: Document TEST macro and state TST_RET/ERR rule LTP-002 Richard Palethorpe
2021-07-14 11:16 ` Petr Vorel
2021-07-14 13:37 ` Richard Palethorpe
2021-07-14 7:11 ` [LTP] [PATCH v2 6/8] Reference LTP-002 rule in Cocci scripts Richard Palethorpe
2021-07-14 11:18 ` Petr Vorel
2021-07-14 7:11 ` [LTP] [PATCH v2 7/8] API: Move libtsc.h from realtime tests include to tst_tsc.h Richard Palethorpe
2021-07-14 11:21 ` Petr Vorel
2021-07-14 7:11 ` [LTP] [PATCH v2 8/8] API/tst_tsc: Add guards and remove some boilerplate Richard Palethorpe
2021-07-14 11:22 ` Petr Vorel
2021-07-14 11:23 ` [LTP] [PATCH v2 0/8] Sparse based checker and rule proposal Petr Vorel
2021-07-14 13:43 ` 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=87y2a9nixg.fsf@suse.de \
--to=rpalethorpe@suse.de \
--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