From: Steve French <smfrench@austin.rr.com>
To: linux-kernel@vger.kernel.org
Subject: recommended sparse checks on kernel code
Date: Thu, 03 Nov 2005 16:03:23 -0600 [thread overview]
Message-ID: <436A892B.9080806@austin.rr.com> (raw)
Are there other interesting/useful sparse checks that can be done beyond
make C=2 -Wbitwise
for kernel code? Is that the maximum checks that sparse can do without
hacking it up?
reply other threads:[~2005-11-03 22:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=436A892B.9080806@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=linux-kernel@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 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.