mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "R, Durgadoss" <durgadoss.r@intel.com>
Cc: "Zhang, Rui" <rui.zhang@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Thermal: Update binding logic based on platform data
Date: Wed, 26 Sep 2012 20:20:30 +0300	[thread overview]
Message-ID: <20120926172029.GQ13767@mwanda> (raw)
In-Reply-To: <4D68720C2E767A4AA6A8796D42C8EB591D3756@BGSMSX101.gar.corp.intel.com>

On Wed, Sep 26, 2012 at 02:39:22PM +0000, R, Durgadoss wrote:
> Hi,
> 
> > -----Original Message-----
> > From: Dan Carpenter [mailto:dan.carpenter@oracle.com]
> > Sent: Wednesday, September 26, 2012 1:58 AM
> > To: R, Durgadoss
> > Cc: Zhang, Rui; linux-kernel@vger.kernel.org
> > Subject: re: Thermal: Update binding logic based on platform data
> > 
> > Hello Durgadoss R,
> > 
> > This is a semi-automatic email about new static checker warnings.
> > 
> > The patch 9b70dfa68ae8: "Thermal: Update binding logic based on
> > platform data" from Sep 18, 2012, leads to the following Smatch
> > complaint:
> 
> looking into this. Will submit appropriate fix patches soon.
> 
> Is there a way for me to check/verify these kind of warnings from
> my side ? This way, I can do the check before I submit each patch.
> 

Sure:

git clone git://repo.or.cz/smatch.git
cd smatch
make
(no make install needed)
cd /to/kernel/src/
~/path/to/smatch/smatch_scripts/kchecker drivers/thermal/thermal_sys.c

regards,
dan carpenter


  reply	other threads:[~2012-09-26 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 20:27 Dan Carpenter
2012-09-26 14:39 ` R, Durgadoss
2012-09-26 17:20   ` Dan Carpenter [this message]
2012-09-27  6:13     ` R, Durgadoss

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=20120926172029.GQ13767@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=durgadoss.r@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /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

Powered by JetHome