From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: David Airlie <airlied@linux.ie>, Jammy Zhou <Jammy.Zhou@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Rex Zhu <Rex.Zhu@amd.com>,
dri-devel@lists.freedesktop.org, kernel-janitors@vger.kernel.org,
Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: drm/amd/powerplay: fix a reversed condition
Date: Tue, 05 Jan 2016 12:36:58 +0000 [thread overview]
Message-ID: <568BB8EA.7070301@users.sourceforge.net> (raw)
In-Reply-To: <20160105111422.GB23363@mwanda>
> Yes. This was a Smatch warning
Thanks for this acknowledgement.
How do you think about to indicate such a detail more often in
your update suggestions and bug reports?
Would it make sense to mark contributions from automatic static
source code analysis by a dedicated tag in the commit message?
> but Coccinelle can also find this kinds of inconsistent NULL checking.
Should we try together to extend the script collection for the
semantic patch language around such use cases?
Regards,
Markus
prev parent reply other threads:[~2016-01-05 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 20:42 [patch] drm/amd/powerplay: fix a reversed condition Dan Carpenter
2016-01-04 21:17 ` Alex Deucher
2016-01-05 9:06 ` SF Markus Elfring
2016-01-05 11:14 ` Dan Carpenter
2016-01-05 12:36 ` SF Markus Elfring [this message]
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=568BB8EA.7070301@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=Jammy.Zhou@amd.com \
--cc=Rex.Zhu@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=dan.carpenter@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=julia.lawall@lip6.fr \
--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