From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] fixup! dmaengine: pxa_dma: add debug information
Date: Fri, 29 May 2015 14:43:45 +0530 [thread overview]
Message-ID: <20150529091345.GE3140@localhost> (raw)
In-Reply-To: <1432761820-32072-1-git-send-email-robert.jarzmik@free.fr>
On Wed, May 27, 2015 at 11:23:40PM +0200, Robert Jarzmik wrote:
> This fixes the following error:
> drivers/dma/pxa_dma.c: In function ?dbg_show_requester_chan?:
> drivers/dma/pxa_dma.c:192:2: error: void value not ignored as it ought to be
> pos += seq_printf(s, "DMA channel %d requester :\n", phy->idx);
> ^
> drivers/dma/pxa_dma.c:197:8: error: void value not ignored as it ought to be
> !!(drcmr & DRCMR_MAPVLD));
> ^
> scripts/Makefile.build:258: recipe for target 'drivers/dma/pxa_dma.o' failed
Applied now, but not pleased that you sent broken code. Sending stuff that
compiles is basic step
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fixup! dmaengine: pxa_dma: add debug information
Date: Fri, 29 May 2015 14:43:45 +0530 [thread overview]
Message-ID: <20150529091345.GE3140@localhost> (raw)
In-Reply-To: <1432761820-32072-1-git-send-email-robert.jarzmik@free.fr>
On Wed, May 27, 2015 at 11:23:40PM +0200, Robert Jarzmik wrote:
> This fixes the following error:
> drivers/dma/pxa_dma.c: In function ‘dbg_show_requester_chan’:
> drivers/dma/pxa_dma.c:192:2: error: void value not ignored as it ought to be
> pos += seq_printf(s, "DMA channel %d requester :\n", phy->idx);
> ^
> drivers/dma/pxa_dma.c:197:8: error: void value not ignored as it ought to be
> !!(drcmr & DRCMR_MAPVLD));
> ^
> scripts/Makefile.build:258: recipe for target 'drivers/dma/pxa_dma.o' failed
Applied now, but not pleased that you sent broken code. Sending stuff that
compiles is basic step
--
~Vinod
next prev parent reply other threads:[~2015-05-29 9:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 21:23 [PATCH] fixup! dmaengine: pxa_dma: add debug information Robert Jarzmik
2015-05-27 21:23 ` Robert Jarzmik
2015-05-28 8:44 ` Arnd Bergmann
2015-05-28 8:44 ` Arnd Bergmann
2015-05-29 9:13 ` Vinod Koul [this message]
2015-05-29 9:13 ` Vinod Koul
2015-05-29 9:29 ` robert.jarzmik at free.fr
2015-05-29 9:29 ` robert.jarzmik
2015-05-29 9:51 ` Joe Perches
2015-05-29 9:51 ` Joe Perches
2015-06-01 21:31 ` Robert Jarzmik
2015-06-01 21:31 ` Robert Jarzmik
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=20150529091345.GE3140@localhost \
--to=vinod.koul@intel.com \
--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.