dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Mark yao <mark.yao@rock-chips.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: drm: rockchip: Add basic drm driver
Date: Wed, 17 Dec 2014 15:42:54 +0300	[thread overview]
Message-ID: <20141217124254.GP4911@mwanda> (raw)
In-Reply-To: <5490D4B9.6070805@rock-chips.com>

On Wed, Dec 17, 2014 at 08:56:25AM +0800, Mark yao wrote:
> Hello Dan,
> 
> Thanks for your review, I will fix it soon.
> Do you use a script to find out these issues? I was interested in
> this script.
> Can you teach me how to find this script and use it?

The first one is a smatch warning.  http://smatch.sf.net.  The other one
is from a private Smatch check that I haven't pushed yet.

regards,
dan carpenter

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2014-12-17 12:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 11:51 drm: rockchip: Add basic drm driver Dan Carpenter
2014-12-17  0:56 ` Mark yao
2014-12-17 12:42   ` Dan Carpenter [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=20141217124254.GP4911@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=mark.yao@rock-chips.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