From: Vinod Koul <vinod.koul@intel.com>
To: Baoyou Xie <baoyou.xie@linaro.org>
Cc: dan.j.williams@intel.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, arnd@arndb.de,
xie.baoyou@zte.com.cn
Subject: Re: [PATCH 1/3] dmaengine: virt-dma: move function declarations
Date: Sat, 1 Oct 2016 11:42:16 +0530 [thread overview]
Message-ID: <20161001061216.GE2467@localhost> (raw)
In-Reply-To: <1474691825-15068-1-git-send-email-baoyou.xie@linaro.org>
On Sat, Sep 24, 2016 at 12:37:05PM +0800, Baoyou Xie wrote:
> We get 2 warnings when building kernel with W=1:
> drivers/dma/virt-dma.c:22:14: warning: no previous prototype for 'vchan_tx_submit' [-Wmissing-prototypes]
> drivers/dma/virt-dma.c:52:5: warning: no previous prototype for 'vchan_tx_desc_free' [-Wmissing-prototypes]
>
> In fact, these two functions are incorrectly declared in a function.
>
> So this patch moves function declarations out of this function.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2016-10-01 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 4:37 [PATCH 1/3] dmaengine: virt-dma: move function declarations Baoyou Xie
2016-09-24 9:07 ` Arnd Bergmann
2016-10-01 6:12 ` Vinod Koul [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=20161001061216.GE2467@localhost \
--to=vinod.koul@intel.com \
--cc=arnd@arndb.de \
--cc=baoyou.xie@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xie.baoyou@zte.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