From: SF Markus Elfring <elfring@users.sourceforge.net>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Cocci] correct handling of return values
Date: Thu, 29 Jul 2010 08:18:19 +0000 [thread overview]
Message-ID: <4C51394B.2060306@users.sourceforge.net> (raw)
> I'm currently working on this task:
> http://kernelnewbies.org/KernelJanitors/Todo/ReturnCodes
>
> I think this task can be partly done with coccinelle. The most often cases of
> invalid handling is no handling :)
>
> I am not guru of coccinelle, but I think it is very useful here. So,
> I've written basic script of finding common errors, but it is not ideal.
Were any improvements achieved since my request "Detection of ignored function
return values" that will help in this use case?
http://lists.diku.dk/pipermail/cocci/2010-February/000690.html
http://www.mail-archive.com/cocci@diku.dk/msg00157.html
Regards,
Markus
next reply other threads:[~2010-07-29 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 8:18 SF Markus Elfring [this message]
2010-07-29 8:56 ` [Cocci] correct handling of return values Julia Lawall
2010-08-07 13:14 ` Nicolas Palix
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=4C51394B.2060306@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=kernel-janitors@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