From: Dan Carpenter <dan.carpenter@oracle.com>
To: micky <micky_ching@realsil.com.cn>
Cc: linux-mmc@vger.kernel.org
Subject: Re: mmc: rtsx: add support for pre_req and post_req
Date: Tue, 25 Feb 2014 10:59:28 +0300 [thread overview]
Message-ID: <20140225075928.GS26776@mwanda> (raw)
In-Reply-To: <530BF74C.4010603@realsil.com.cn>
On Tue, Feb 25, 2014 at 09:52:12AM +0800, micky wrote:
> Hi Dan,
>
> I'm wondering how to get this warning info, so I can check before
> sending patch.
> Can you give me some idea?
>
This is a smatch thing, but you it's a cross function bug so you have to
build the database first and that takes some hours. The commands are
simple though. Run:
~/path/to/smatch_scripts/build_kernel_data.sh
~/path/to/smatch_scripts/kchecker drivers/mmc/host/rtsx_pci_sdmmc.c
regards,
dan carpenter
next prev parent reply other threads:[~2014-02-25 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 22:03 mmc: rtsx: add support for pre_req and post_req Dan Carpenter
2014-02-25 1:52 ` micky
2014-02-25 7:59 ` Dan Carpenter [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-24 22:03 Dan Carpenter
2014-02-28 20:35 Dan Carpenter
2014-03-03 1:13 ` micky
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=20140225075928.GS26776@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-mmc@vger.kernel.org \
--cc=micky_ching@realsil.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).