From: Vinod Koul <vinod.koul@intel.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Russell King <rmk+kernel@arm.linux.org.uk>,
peter@hurleysoftware.com, Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
nsekhar@ti.com, linux-omap@vger.kernel.org,
linux-serial@vger.kernel.org, john.ogness@linutronix.de,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: [PATCH 2/3] dma: add __must_check annotation for dmaengine_pause()
Date: Tue, 11 Aug 2015 15:28:52 +0530 [thread overview]
Message-ID: <20150811095852.GW11789@localhost> (raw)
In-Reply-To: <1438977619-15488-3-git-send-email-bigeasy@linutronix.de>
On Fri, Aug 07, 2015 at 10:00:18PM +0200, Sebastian Andrzej Siewior wrote:
> In 8250-omap I learned it the hard way that ignoring the return code
> of dmaengine_pause() might be bad because the underlying DMA driver
> might not support the function at all and so not doing what one is
> expecting.
> This patch adds the __must_check annotation as suggested by Russell King.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> include/linux/dmaengine.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
> index 8ad9a4e839f6..4eac4716bded 100644
> --- a/include/linux/dmaengine.h
> +++ b/include/linux/dmaengine.h
> @@ -825,7 +825,7 @@ static inline int dmaengine_terminate_all(struct dma_chan *chan)
> return -ENOSYS;
> }
>
> -static inline int dmaengine_pause(struct dma_chan *chan)
> +static inline int __must_check dmaengine_pause(struct dma_chan *chan)
> {
> if (chan->device->device_pause)
> return chan->device->device_pause(chan);
Give that there are bunch of users of this call which may or maynot be using
this, I think putting this check is too stringent
--
~Vinod
next prev parent reply other threads:[~2015-08-11 9:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 20:00 omap-dma + 8250_omap: fix the dmaengine_pause() Sebastian Andrzej Siewior
2015-08-07 20:00 ` [PATCH 1/3] tty: serial: 8250_omap: do not use RX DMA if pause is not supported Sebastian Andrzej Siewior
2015-08-08 0:28 ` Peter Hurley
2015-08-08 9:03 ` Russell King - ARM Linux
2015-08-11 9:57 ` Vinod Koul
2015-08-08 9:32 ` Sebastian Andrzej Siewior
2015-08-08 9:57 ` Russell King - ARM Linux
2015-08-08 15:40 ` Greg KH
2015-08-10 11:54 ` Peter Ujfalusi
2015-08-10 12:19 ` Sebastian Andrzej Siewior
2015-08-10 13:00 ` Peter Hurley
2015-08-10 17:15 ` Russell King - ARM Linux
2015-08-07 20:00 ` [PATCH 2/3] dma: add __must_check annotation for dmaengine_pause() Sebastian Andrzej Siewior
2015-08-08 0:40 ` Peter Hurley
2015-08-11 9:58 ` Vinod Koul [this message]
2015-08-11 10:06 ` Russell King - ARM Linux
2015-08-11 12:34 ` Sebastian Andrzej Siewior
2015-08-21 8:32 ` Vinod Koul
2015-08-07 20:00 ` [PATCH v3 3/3] dma: omap-dma: add support for pause of non-cyclic transfers Sebastian Andrzej Siewior
2015-08-11 12:02 ` Peter Ujfalusi
2015-08-11 12:30 ` Russell King - ARM Linux
2015-08-11 12:43 ` Peter Ujfalusi
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=20150811095852.GW11789@localhost \
--to=vinod.koul@intel.com \
--cc=bigeasy@linutronix.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=peter@hurleysoftware.com \
--cc=rmk+kernel@arm.linux.org.uk \
/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).