From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vinod Koul <vkoul@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
YueHaibing <yuehaibing@huawei.com>
Subject: linux-next: build warning after merge of the slave-dma tree
Date: Fri, 14 Feb 2020 11:00:39 +1100 [thread overview]
Message-ID: <20200214110039.51369fae@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Hi all,
After merging the slave-dma tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/dma/sun4i-dma.c: In function 'sun4i_dma_prep_dma_cyclic':
drivers/dma/sun4i-dma.c:30:51: warning: statement with no effect [-Wunused-value]
30 | #define SUN4I_DMA_CFG_SRC_ADDR_MODE(mode) ((mode) << 5)
| ~~~~~~~~^~~~~
drivers/dma/sun4i-dma.c:701:8: note: in expansion of macro 'SUN4I_DMA_CFG_SRC_ADDR_MODE'
701 | SUN4I_DMA_CFG_SRC_ADDR_MODE(linear_mode);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
Introduced by commit
6ebb827f7aad ("dmaengine: sun4i: use 'linear_mode' in sun4i_dma_prep_dma_cyclic")
Please do not ignore/dismiss new warnings ... this one points out a real issue.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-02-14 0:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 0:00 Stephen Rothwell [this message]
2020-02-14 4:41 ` linux-next: build warning after merge of the slave-dma tree Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2019-08-12 7:14 Stephen Rothwell
2019-08-12 9:14 ` Arnd Bergmann
2019-08-12 9:21 ` Stephen Rothwell
2018-11-26 5:59 Stephen Rothwell
2018-11-26 8:09 ` Vinod Koul
2018-09-13 2:22 Stephen Rothwell
2018-09-13 7:17 ` Angelo Dureghello
2018-07-04 3:30 Stephen Rothwell
2018-07-04 4:20 ` Vinod
2018-07-05 2:47 ` Stephen Rothwell
2018-07-05 5:01 ` Vinod
2016-06-09 1:18 Stephen Rothwell
2016-06-09 6:04 ` Appana Durga Kedareswara Rao
2015-03-30 6:20 Stephen Rothwell
2015-03-30 6:26 ` Appana Durga Kedareswara Rao
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=20200214110039.51369fae@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=vkoul@kernel.org \
--cc=yuehaibing@huawei.com \
/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).