From: Vinod Koul <vinod.koul@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Dan Williams <dan.j.williams@intel.com>,
Sinan Kaya <okaya@codeaurora.org>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: qcom_hidma: hide MSI handler when unused
Date: Mon, 14 Nov 2016 10:54:27 +0530 [thread overview]
Message-ID: <20161114052426.GZ3000@localhost> (raw)
In-Reply-To: <20161108134937.1966206-1-arnd@arndb.de>
On Tue, Nov 08, 2016 at 02:48:59PM +0100, Arnd Bergmann wrote:
> The newly added MSI support causes a harmless warning when MSI
> is disabled:
>
> drivers/dma/qcom/hidma.c:558:20: error: 'hidma_chirq_handler_msi' defined but not used [-Werror=unused-function]
>
> This adds another #ifdef to match that around the users of the function.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2016-11-14 5:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 13:48 [PATCH] dmaengine: qcom_hidma: hide MSI handler when unused Arnd Bergmann
2016-11-08 14:42 ` Sinan Kaya
2016-11-14 5:24 ` 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=20161114052426.GZ3000@localhost \
--to=vinod.koul@intel.com \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okaya@codeaurora.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 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).