From: zhangfei.gao@linaro.org (zhangfei)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] dmaengine: add interface of dma_get_slave_channel
Date: Tue, 27 Aug 2013 10:04:48 +0800 [thread overview]
Message-ID: <521C0940.9000408@linaro.org> (raw)
In-Reply-To: <20130820081348.GV4713@mwanda>
On 13-08-20 04:13 PM, Dan Carpenter wrote:
> On Tue, Aug 20, 2013 at 03:58:41PM +0800, zhangfei gao wrote:
>
>> BTW, it is strange I do not see such compile warning here :(
>
> This was a Smatch static checker warning, not a regular build
> warning.
>
> regards,
> dan carpenter
>
Dear Dan
Thanks for introducing this valuable tool.
Have download from git://repo.or.cz/smatch.git
When trying use this tool, could get some warning,
make CHECK="~/bin/smatch -p=kernel --no-data" C=1 | tee warns.txt
Also some strange warning, like "SQL error #2: no such table:
caller_info", is it ignored?
Besides, when test this case for check smatch setting.
Still not reproduce the issue, should be not config correct?
Only get
drivers/dma/dmaengine.c:845 dma_async_device_register() warn: possible
memory leak of 'idr_ref'
drivers/dma/dmaengine.c:866 dma_async_device_register() warn: possible
memory leak of 'idr_ref'
Anyway, though config not totally correct, it really could find some
warning.
Thanks
next prev parent reply other threads:[~2013-08-27 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 7:02 [PATCH v3 0/2] dmaengine: add k3dma Zhangfei Gao
2013-08-15 7:02 ` [PATCH v3 1/2] dmaengine: add interface of dma_get_slave_channel Zhangfei Gao
2013-08-19 5:25 ` Vinod Koul
2013-08-20 7:58 ` zhangfei gao
2013-08-20 8:13 ` Dan Carpenter
2013-08-20 8:22 ` Vinod Koul
2013-08-27 2:04 ` zhangfei [this message]
2013-09-03 20:39 ` Dan Carpenter
2013-08-20 8:22 ` Vinod Koul
2013-08-15 7:02 ` [PATCH v3 2/2] dmaengine: Add hisilicon k3 DMA engine driver Zhangfei Gao
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=521C0940.9000408@linaro.org \
--to=zhangfei.gao@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.